Atlassian Jira vs. Modern Requirements4DevOps

Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.

Incentivized

We tried the Modern Requirements4DevOps AddIn to see if it brings a added value to our development. I have to say that I would distinguish between types of projects in which it is beneficial and in which it is probably "over engineering". Certainly, bigger development projects with higher complexity are more suitable than small and not really complex projects. However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.

Incentivized

• As a developer, it is easy to create, track and manage tickets efficiently.
• Customizable issue types (eg: Bug, Task, Story, Epic) allow teams to categorize and priorizate work.
• Great text editor and markdown support for detailed issue descriptions.
• Assign issues to team members, set due dates and define priorities.
• Integration with Jenkins, GitHub and other CI/CD tools to automate builds and deployments.

Incentivized

• Smart Documents
• Building a connection between individual entities (requirements, documents, tasks, tests)
• Requirements Management and Reporting

Incentivized

• The interface is not intuitive to learn for new users
• JQL is similarly challenging for newbies
• It's possible to accidentally move issues from one sprint to another without realizing your mistake
• Certain issue attributes aren't available in certain view (e.g. story points from the epic overview)

Incentivized

• forms could be transferred into in line fields to allow in line maintenance of data
• make window management of diagram builder more flexibility to make more space to build diagrams
• I would wish that the performance is a bit better sometimes, loading times can be quite long in some cases

Incentivized

JIRA is highly integrated into our organization. Nearly every department uses it, and many have multiple JIRA projects set up to track different types of work. We rolled out JIRA in a staged manner, but it continued to be adopted by more and more people and departments because it continues to show results. I expect we will continue to renew our JIRA license for years to come

Incentivized

Atlassian Jira is relatively easy to use, but there are several ways to configure it, which can make it more complicated if you configure it incorrectly. Keeping the customizations and complexity limited to being the project would be suggested to ensure you don't lose in-built Atlassian Jira features, then change the configuration as you find things aren't meeting your exact needs.

Incentivized

Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.

Incentivized

Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good

Incentivized

I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.

Incentivized

Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own

Incentivized

One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.

Incentivized

Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.

Incentivized

Jira is more feature-rich than Trello and also has better integration with other tools. Trello is a lot more focused on work tracking, while Jira can do a lot more than that. Both can also be combined, although they're often considered mutually exclusive alternatives—I've seen cases where companies choose to use either one or the other, but I haven't met an actual case of a company using both.

Incentivized

Modern Requirements4DevOps is an AddIn for Azure DevOps Server (Microsoft Azure DevOps) and extends the native features of Azure DevOps in the area of Requirements Engineering, Requirements Management and Reporting. Azure DevOps already contains tons of valuable features. However, for bigger and more complex projects Modern Requirements4DevOps extends Azure DevOps by further features. Thus we used both products alongside.

Incentivized

Atlassian Jira is highly stable and good with its performance and its has all the required scalability features as business needs

Incentivized

• JIRA has increased the teams' productivity and efficiency; the sprint timelines have improved by 15-20%.
• JIRA's integration with tools like Bitbucket and Confluence has improved functional collaboration, leading to faster decision-making and issue resolution by approximately 10-15%.
• Additional functionality requires additional third-party plugins, which require additional costs; the requirements of these plugins increase the costs by approximately 15%.

Incentivized

• Better communication --> thus less misunderstandings
• More Transparency about requirements --> adds context and helps to build a common understanding
• Traceability of Requirements --> we used the baseline also to look into the history of requirements to understand how certain requirements have changed

Incentivized