Overall Satisfaction with Jira Software
We use it to enter all requests; vet their research thru discovery; assign resources, points, sprint, deadlines, watchers, labels, components, etc.; publicize progress to all parties; configure dashboards to enable managers to make decisions; and house all our historical works for future reference. It is in the cloud thus accessible from anywhere. Our centralized directory runs its single-sign on thus no need to make accounts. User data from that directory is shown in JIRA thus speeding up contacting. It solves lack of mutual visibility, accountability, standardizing tags/labels, mass assigning tasks, organizing a formerly email-based workflow, and forces discipline.
- Labels enable all the benefits of tagging-based organizing
- Webhook with Git means we can see all commits per task(s) cited in the commit message
- Easy single-sign on integration removes need to create new accounts
- Frontend is super fast which promotes users taking even complex tagging actions
- No problems integrating with Confluence (Wiki-like) and BitBucket (Git-like) for productive quick starts.
- Mass-editing and scripting to, say, mass-rename a set of labels to a new one or many
- Command line interface would be nice, for power users
- Version number is difficult to find leading to difficulty judging what version we run thus which features we are truly missing
- Eorkflow edits aren't protected from errors/inconsistencies like mapping a label to null
- Workflows can be loop-to-self, be massively inefficient, should be a workflow "linter"
- All 2,400 users can see the progress of any employee anywhere in the firm in the clear without delay
- Fast interface means ease of use which makes users want to file even the seemingly smallest idea so we have better feedback and nothing is lost
- Significant integration (sso, Git webhook, etc.) means we've confidence JIRA will adapt to even future systems
- Prospective employees often use it & thus no delay in their using the ticketing system with confidence
- Trac and Bugzilla
Trac is as basic as the subversion with which it's often associated in feature set, requires signifiant time and patience to set up much less customize/configure, and is being abandoned by most industry folks. Bugzilla is a classic solution which holds up, but has an interface which causes non-developer users to not want to use it. Interface counts for first impressions and confidence which are big, especially for non-tech departments of which most of ours are.
Do you think Jira Software delivers good value for the price?
Yes
Are you happy with Jira Software's feature set?
Yes
Did Jira Software live up to sales and marketing promises?
Yes
Did implementation of Jira Software go as expected?
Yes
Would you buy Jira Software again?
Yes