Digital.ai TeamForge vs. Jira Work Management

CollabNet TeamForge is more well-suited for technically knowledgeable users such as developers, systems analysts, QA but not for non-technical users due to the technical data used throughout the tool. CollabNet TeamForge is appropriate for most applications development. In any industry especially suited for high demand software delivery environments.

Incentivized

Jira Work Management suits projects involving multiple teams, such as product development. In our case, the design, development, and QA teams use Jira to track tasks from ideation to deployment. Custom workflows and real-time updates ensure that all teams are on the same page, and the ability to link related tasks helps manage dependencies effectively.

Incentivized

• Code security.
• Code migration.
• Agile tie-in.

Incentivized

• Provide a roadmap of all epics
• Provide a backlog in which you can see all the possible work to be done to create your sprint plan
• Have all our projects within reach
• Have a dashboard with editable columns to manage your work
• Be able to filter by person
• Be able to see past sprints

• I would like to see personalization for managing artifacts, that is, allowing the user to customize pages and save personalized settings and then save them as bookmarks.
• I would like an improved subversion browser such as a graphical user interface rather than a basic file explorer.
• I would like built in features for CollabNet TeamForge integrated with subversion so that i can associate my private code branches and code changes.

Incentivized

• More clarification on where to find useful tools and resources for new users.
• Breakdown of Projects, Tasks, Sub-tasks, bugs is hard to follow and cannot be changed once created.
• The ability to customize the dashboard/home page to fit the needs of individuals could use some work.

Incentivized

As we are Atlassian users overall, this entire ecosystem is truly built from a 360 perspective. It becomes the one source of truth, and we can easily see where we are in our projects and where to emphasize focus in the upcoming period. There are some areas for minor improvements, but they are more a matter of preference rather than business necessity

Incentivized

They always answer the phone when we put a call in, any time. They have consistently sent out contractors when needed and were there every step of the way when we switched over from ClearCase to TeamForge years ago. The support is what you really pay for when you buy into TeamForge.

Incentivized

CollabNet TeamForge is superior to Mercury mainly because it has a subversion change management tool integrated with the product. CollabNet TeamForge offers more complexity but with more flexibility for managing and tracking projects. I think
CollabNet TeamForge is more comprehensive than either Mercury and JIRA. They're all user friendly tools with short learning curves but CollabNet TeamForge is most efficient in my experience.
JIRA was recently adopted for particular applications and is currently being evaluated by various technology teams.

Incentivized

The evolution of Jira Service Desk to Jira work management is accompanied by lot of new features like the List View which allows inline editing, easy column management, the Calendar View bases on extensible modal and state categories, the Timeline View supports tasks and subtasks, the Boards which allow the categorization of status and allow the visibility of subtasks on the cards, Forms can be created very easily, Project templates can be used based on the business area.

Incentivized

• Unfortunately, I do not have access to ROI information.

Incentivized

• For our marketing team, Jira Work Management caused us to lose valuable work time due to manual updates that could have been automated.
• Due to lack of creative review tools within Jira Work Management, our team had to pursue other tools that do not integrate with Jira Work Management, thus creating additional OpEx.

Incentivized