Atlassian Jira vs. Rocket DevOps

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

Rocket Aldon is perfect for simple changes to traditional IBM i development using RPGLE, CL, and DDS. It is great for finding related objects that are referenced in many locations and helping recompile all of these objects. However, Aldon has a particularly hard time with SQL views. For some reason, it is determined to lock every table related to a view even though this is not required by the operating system. Whenever one view references another view, you are always in danger of losing a view permanently if you didn't check it out and promote it. To clarify, imagine you created a view CUSTOMER_INFO. Then you make another view called CUSTOMER_SHIPMENTS that joins the CUSTOMER_INFO to a shipping table. If you ever change CUSTOMER_INFO and then promote it, there is a good chance that Aldon will delete the CUSTOMER_SHIPMENTS view and you will not get a single warning. It doesn't happen every time but when it does you are going to have a real mess on your hands.

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

• Software Change Management
• IBM i development
• Object relationships

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

• Check-in checkout process can be cumbersome
• UI is crowded and not intuitive
• Requires in house expertise maintain and manage

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

Based on current integration with our release process, we will need to keep this for the future.

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

Support is hit and miss. Sometimes they give some great assistance and sometimes they are no help at all. It always seems like they can't replicate the problem but then they never try to get on our system to do deeper research. It's kind of frustrating dealing with them. Also, the website isn't that helpful.

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

There are not a lot of CMS solutions for the IBM i server. Midrange Dynamics MDCMS is definitely one to consider. It seems very similar to Aldon Rocket and has a lot more functionality. I haven't used it but I have been to a demo and it looks promising. It seems a lot more intuitive and the promotions seem easier. However, that was a demo environment and even then it crashed so there's that to consider....

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

• Software promotion is much easier and doesn't require custom coding.
• Developers can work collaboratively with less overlap.
• Developers can find objects faster and research code more thoroughly.

Incentivized