Overall Satisfaction with Jira Software
Jira is being used across the entire organization for different needs.
The R&D team is the main "heavy" consumer to manage the development of our software, but Jira is also being used by other teams like product, graphics, support, customer success etc. It let's us collaborate and prioritize our daily tasks while maintaining transparency between teams.
The R&D team is the main "heavy" consumer to manage the development of our software, but Jira is also being used by other teams like product, graphics, support, customer success etc. It let's us collaborate and prioritize our daily tasks while maintaining transparency between teams.
- Project management.
- Knowledge sharing.
- Time management and prioritization.
- The software is too "old school" - the UX can be improved.
- Since it's very flexible, it's also difficult to administer and make changes.
- It sometimes has performance issues during work.
- Project management (tasks, bugs, etc.).
- Knowledge sharing (among R&D, product and support for example).
- The advanced search capabilities.
Redmine was used at the very beginning when we were a really small team.
Pivotal Tracker was next, and although it has a better UX features, it lacks the ability to manage big projects in parallel (at least back in the days).
Jira is far more flexible for adjustments to our teams' needs in terms of project management of different types.
Pivotal Tracker was next, and although it has a better UX features, it lacks the ability to manage big projects in parallel (at least back in the days).
Jira is far more flexible for adjustments to our teams' needs in terms of project management of different types.
Do you think Jira Software delivers good value for the price?
Yes
Are you happy with Jira Software's feature set?
No
Did Jira Software live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Jira Software go as expected?
Yes
Would you buy Jira Software again?
Yes