JIRA - adapts to your software development process!
Updated July 31, 2019
JIRA - adapts to your software development process!

Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with JIRA Software
JIRA has been a great replacement for Microsoft Team Foundation Server. Not only is it easier to use, but it's highly customizable by our organization without the need of external consultants. Bugs or feature requests are created throughout the whole company and then triaged into actionable tasks. The filter feature on the system dashboard helps a lot in this context.
Pros
- Custom search queries can be saved and shared as filters.
- Batch operations on tickets work well and you can choose if you want to notify others.
- Ticket fields are highly customizable for easier creation.
Cons
- Some operations take their time.
- Default ticket settings are too complicated and complex for simple use cases.
- Basically, there is no "one go to process". You can pick Kanban, Scrum, ... whatever you like. The user interface, therefore, looks quite mixed up on some occasions.
- Development pace has been greatly improved.
- Visibility of progress for better understanding of the development process.
- End users are more likely to open up feature requests or bug reports.
Integration with 3rd party plugins works really well and improves the feature set of JIRA itself. We combine JIRA together with BigBrassBand's git module and bug reports from Usersnap, which help greatly, because of the attached screenshot.
Team Foundation Server was very hard to use and user adoption was negligible, although there was an integration with Visual Studio.
Team Foundation Server was very hard to use and user adoption was negligible, although there was an integration with Visual Studio.
Comments
Please log in to join the conversation