Jira is great for what it's good at!
July 29, 2016
Jira is great for what it's good at!
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with JIRA Software
Across all software development teams, we use Jira for work including: defects, stories, epics, dependency mapping, etc. Each team has their own Jira project and their own boards (Agile board or Kanban boards) and the projects in Jira are maintained by Project Leaders. Jira is heavily used by QA for defects and story verification. It is also used by analysts and product owners for story and requirement communication to development teams.
- Tracking hierarchy and linking for Epics -> Stories -> Defects.
- Linking stories in one team's Jira project to another project, due to dependencies needed for enterprise software development.
- Flexibility in set up and workflows can vary by team, and can be customized by that team.
- I'd love to be able to customize further what types of data shows in different views (e.g. Backlog vs. Agile Board).
- I'd like to see more data in the links between stories, as well, so that you can see more info without having to link out to the other story and view.
- Jira is definitely quicker to learn and easier to use than a variety of other products that we've used, so the ease of adoption is great.
- I do wish it was easier to maintain certain information (priorities, previously scheduled/committed dates, etc.) - if it could do that, it would be more valuable to our organization.
- It's a great ROI that users can easily add images, videos, or other artifacts to the Jira items themselves.
Using JIRA Software
Pros | Cons |
---|---|
Like to use Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |