Overall Satisfaction with Jira Service Desk
- Used across the whole organization.
- Project Requirements repository - agile/waterfall.
- QA tracking during test case resolution.
- Process improvement.
- Keeps track of all activities related to the project in question.
- Documentation of Requirements - serves as the go-to source for all requirements created as a result of the SDS (System Design Specifications) review and sign-off.
- Process improvement - We used to revamp failing processes and centrally locate all BAU (business as usual) developments tickets through JIRA.
- Bug tracking - Great source for defect tracking and resolution.
- Historical repository - we use as a historical reference and document location for all projects.
- Add-ons - Some things I think should be easier to find and possibly more documentation.
- Traceability linkage - JIRA has a hierarchy - EPIC/Story/Bugs etc. - They should automatically be linked one to the other once users attach for example a bug to a story - I.E. Cannot close the story until the bug has been resolved.
- Better linkage to MS office tools - I.E> MS Project/Excel - I find it tricky to drop excel file into JIRA.
- Not in a position to comment
- Not in a position to comment
- Not in a position to comment
- Rally Software (formerly CA Agile Central) and Azure DevOps Server (formerly Team Foundation Server)
JIRA stacks up very well in particular with Microsoft Team Foundation Server which I used extensively for 7 years. The transition I had to do to JIRA was seamless and they both compliment each other well.