Reviews (1-25 of 120)
- 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"
- Fits right into agile methodology and very easy to use.
- No problems with copy/pasting images, attachments, and formatting stories to look right. Interface is fast, pleasing to use.
- Commenting and tracking conversation and notes on stories is very easy.
- Reporting and some charting capabilities is lacking. Need better ways to track burndown, velocity, etc.
- Missing functionality for tracking testing and pass/fail.
- A good example of "you get what you put in". It can get messy and overwhelming easily if left unchecked. Some tools and study on this would be helpful to guide users on proper management of agile.
1. User stories in form of project backlog
2. Acceptance criteria
3. Creating bugs
4. Analysis ticket
5. Maintaining story workflows (from ready for dev to closed)
6. Logging work hours spent on each individual ticket/story
It is also very helpful in creating a very simplistic boundary line between the on going sprint and the backlog (all my projects have been executed in Agile mode). In addition to it, as my projects have always had more than one sprint going on simultaneously and the stories part of those sprints related to each other, it acts as a very elegant tool for representing such views where the information is easy to comprehend for any developer or tester.
- Single view for all the user stories (active sprint/backlog)
- Ability to generate reports of various types for each of the active / closed sprints for e.g. burndown chart, sprint velocity etc.
- Ability to track release tickets - we can create tickets which are supposed to go for production from various sprints in one single page and manage it from there.
- Integration of communication tools like Hipchat and Slack makes it very easy for tracking & responding to notifications.
- Mobile app of JIRA is not so holistic in nature and one has to navigate a lot to do various things which are very easy to do in web application.
2. If tickets have various labels, one can view the tickets using the labels as the filter.
3. Reports are very easy to generate, they also come in form of pie charts, graphs etc.
4. A dashboard view of all the tracks going on gives a beautiful integrated view of the progress made in the current sprint.
Inappropriate - JIRA reports are not easy to reuse in the sense that the graphical reports generated are not downloadable in form of image and using other techniques leads to resolution issues for those report images.
- The best thing I liked about it were the variety of charts and graphs which helped us to have a clear understanding of our sprint work.
- The ability to create sub tasks for user stories.
- We can also customise or configure the application which helps us to keep the application as common as possible.
- The ability to prioritize the stories in the backlog so as to take it up in a sprint is also beneficial.
- I have nothing as of now which I dislike, will definitely update if I find any. We moved from another application to this, it has been better since then.
- Task Board
- User stories
- Task Assignment
- Filters. I find it hard to try and retrieve task/stories from a specific duration
- Creating dashboards is not intuitive
- Error messages are not user friendly
- Kanban Board - Track the features using workflow methodology.
- Email notification when the ticket is assigned to specific users.
- Filter the the JIRA tickets using keyword search functionality.
- User Interface can be improved more by adopting modern designs.
- Artificial Intelligence can be integrated for automating lots of process.
- Chat functionality also can also be integrated to JIRA for real time communication.
We use it for all purposes. The fields are really extensive and easy to use. Additionally, the filters are very useful and you can track the issues very easily. Filters have advance search features too which incorporate very simple query language and can fetch specific results. Jira dashboards are another feature that is used daily. You can add various gadgets to the dashboard and track the progress of the project instantly. You can also share dashboards with people where they can check the status and this, in turn, saves you time.
- Issue logging and tracking.
- You need to save the filter and basically make it public before using it in the gadget on the dashboard. If it's not public the gadget will not be displayed to any other user. This is a tedious task sometimes.
- There should some way where you can save your formats of bug logging etc. so you don't have to type the same things every time and you can just simply pre-populate the format.
- Great ticketing system for IT.
- JIRA supported my work managing conferences, serving as a workflow management tool, very strong around dependencies.
- Custom templates would be GREAT! I used the same basic template for most conferences I managed but had to recreate it from scratch each time.
- Requires lots of attention and careful use by diligent employees.
JIRA helped our team collaborate on an otherwise overwhelming volume of projects, for example (on my workload alone at any given moment) dozens of active conferences, dozens of upcoming hosted events, 20+ active email/social media campaigns, 5-6 case studies in process, and a dozen or more ongoing prospect mapping projects. For anyone juggling that many diverse tasks it'd be a good fit.
For a use case where daily tasks are more straightforward or cyclical, or where the team is smaller and the details and due dates less numerous, it may be overkill.
- It is very user-friendly.
- Bulk change option is the best thing in JIRA Software. If anything we need to change or update in written test cases, we can easily update all the written test cases by using bulk change option. No need to update manually for each test case. It's very cool and saves time!
- We can attach the photos, videos for the reference in posted bugs.
- We can only upload the files (images, videos) less than 10 MB in size.
- It would be great if we upload the files more than 10 MB size.
- JIRA is not an open-source tool. So it is not possible to use at some start-up companies.
However sometimes when we write test steps in JIRA, it's not quickly updated. It took some time to reflect the written test step.
- JIRA offers a lot of integrations that really improve our work. For example, the Salesforce integration makes it really easy to link Salesforce product roadmap cards (relevant to the entire product team) to an individual JIRA issue (one specific task-relevant to that team).
- JIRA offers very good search and filter functionality. The quick filters make it very easy to immediately see only my own issues. You can create custom views, which are especially helpful for my team during our daily standup, allowing us to only see relevant issues.
- JIRA issues come with lots of customizable fields. Due dates, assignees, labels, priority level, epic link, etc. -- makes it very easy to organize and find specific issues.
- Our team happens to have many steps within the workflow, and therefore we have more columns than other teams. JIRA Software always displays all columns in one static view. Because we have so many columns, each column becomes very skinny and the issues can be difficult to parse. We can't reduce our number of columns, so I wish we had the option to side-scroll instead of fitting all columns into the current browser size.
- We would love the ability to create CLEAR multiple statuses within a column. You can create multiple statuses for a column, but they all appear together and are difficult to distinguish. It isn't possible to move an issue from one status to a different status within the same column. You have to drag the issue into a different column, then drag it back into your chosen status, or change the status using the issue dropdown option.
- A minor nitpick, but I wish I could create an issue and immediately put it into our "To Do" column. Instead, it automatically goes into our backlog. Then I have to go to a different page to move the issue from backlog to To Do.
- JIRA makes collaboration very easy
- JIRA allows us to keep a line of sight on all of the tasks that are on going
- JIRA also allows for easy export of data for reporting and such
- The UI In JIRA is not very intuitive, they have comingled products and navigation is difficult at times
- JIRA can be annoying with the number of email notifications it shoots out
- JIRA's security model is overly complex and can lead to issues
- Jira is powerful and flexible. It can be configured and used in a number of ways and for a number of different use cases. But despite that, we've found it easy to use and we were able to use it without much training.
- For agile-based software development, it makes it easy to manage your backlog, plan sprints, track and manage individual issues, and get reports showing overall team/sprint metrics. All of these features are seamlessly integrated with each other.
- It integrates well with other developer tools like Github and Slack. For example, this makes it easy to view branches and pull requests related to a specific story or automatically notify your team of important status changes to an issue.
- Sometimes there are different modes for editing the same piece of data (like an issue's description) depending on how you're viewing that issue. One mode may use a WYSIWYG editor while the other mode uses plain text with Markdown. This is slightly confusing as the user experience isn't consistent.
- As with most WYSIWYG editors, it can sometimes be difficult to control the formatting the way you want. I've also had issues with it inserting line breaks after hyperlinks sometimes for no apparent reason.
- It is very simple, basic and simple to use.
- It allows precise customizable estimates according to the needs of the project.
- You can have administrative control of the company's activities (projects, processes, procedures).
- It is compatible in virtually all databases.
- It offers Web access with support for the main browsers in the market, email notifications, as well as many applications that provide additional resources to Jira.
- Although Jira is an excellent tool for project management, the cost can be somewhat expensive.
- Its initial configuration proved to be complicated.
- It can be difficult for beginners, because it is difficult to understand its characteristics.
- Project tracking
- Individual task tracking
- Integration with Github
- Communication with team members is adequate but not as good as other software
- Not as many software integrations as I would like
- Can't delete tasks unless you are super user
1 ) a tool supporting internal users or client requests (internal or external service desk/help desk).
2) a teamworking tool for the sharing of software specifications during software development.
- Excellent tool for supporting internal or external users. If you want to start, you can go to the cloud/online subscription which is very cheap and you can start immediately with preconfigured processes
- Great tool for sharing business and IT requirements in SW development. Requires connection of JIRA and Confluence which works fine after initial configuration.
- Available basic reporting of performance of teams or individuals.
- An immediate good overview of severity (priority) of tickets, resolutions KPIs, etc.
- The processes can not be thoroughly analyzed, visualized and managed. Although a basic reporting is available and reports can be customized, the process discovery in a complex environment is not supported. This can, however, be provided by an external process mining application. JIRA can export the data or provides access to its database via API.
- Easy to use bug tracking features.
- It has a great support for Agile SCRUM and Kanban software development methodologies.
- Promotes collaboration within the team and across teams.
- It is extremely configurable and allows a system admin to address complex project management requirements.
- There is a steep learning curve for JIRA administrators before the full potential of the tool can be harnessed.
- The licensing system is per number of users. If you buy a small license and the tool is widely adopted, you may have an issue in getting your budget approved in a low cost environment, because the price for higher tiers goes up quickly.
- Support can use some improvement. It happened few times that for critical issues we had to spend a lot of time exchanging emails and explaining to different people where the problem was.
You could use it for project management as well, for task assignment, resources management, deliveries etc. However, you may find other tools that excel at this compared to JIRA.
- Bug life cycle management.
- Grouping of deliverables as: epic, story, change request, bugs, tickets, enquiries, etc.
- Logging estimates and tracking actual efforts, giving effective variance computation.
- Computing metrics for our projects using the custom fields in JIRA.
- The SLA management is ineffective.
- The assignee has to be an individual, which is a restriction. JIRA needs to enable issue assignment to a group/department as well, to bring it to an issue dashboard.
- Query management can be made easy with some add-ons like 'Script runner' which is currently outside JIRA.
It might be less appropriate with smaller projects as you need to spend some time setting it up etc. The layout and overview can be overwhelming and you need to consider that if you want to include external clients etc who do not have experience with Jira.
- Easily manage workload.
- Get all useful information and links to useful documents.
- Check the status of a project.
- Integration with Git.
- There is no code refactoring plugin.
- We can prioritize the projects.
- The user interface makes it a bit complex to search for all items.
- JIRA Query Language - simple and extremely powerful search for issues.
- User and group management - To manage multiple teams and users is very simple as well.
- Webhooks and ready to use third party integrations like Slack keeps everyone informed about project updates.
- JIRA project work dashboards are very useful and we use it to display on a kiosk where entire team can keep track of issues.
- JIRA gives multiple ready to use project types and customisable issue workflow.
- Promotes Agile methodology
- UI performance can be improved. It still feels slow even after 5 years of using it.
- They could've offered Confluence along with JIRA since it's not reasonable to pay for project documentation separately. We simply use Google docs for that purpose and it's free!
- There is a steep learning curve for tech and non-tech users initially.
- It's mobile support is still very limited!
- Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed.
- Notifications can be automatically sent out (if setup) to the Developer when new work is assigned.
- Epics/Tasks/backlog items can be managed through an easy to use drag and drop process.
- Agile. Easy to work with (very intuitive)
- I don't have anything negative to say about the software.
- As with any software, the GUI can always use improvement, but that comes with time.
- It can lock up very briefly at times due to too many users.
projects within our company. It is a corporate-wide engagement with JIRA
with several businesses that use it independently with a corporate
administrator to manage the tool. We use it for very large projects, like Salesforce
rollouts, as well as smaller projects like minor enhancements or bug fixes across
all key software environments.
- It is a great tool to link documents and documentation to specific user stories to keep things organized.
- It has a great user management feature to help us plug resources into the right projects and remove users as they move on to other work.
- It has sold plug-and-play options that you can elect to use or deselect in order not to cloud the interface.
- The look and feel is a bit sterile, which is both good and bad. Some nice skins to make it easily customizable to our existing corporate color schemes would be nice.
- Cost is always a place for improvement. JIRA is not overly expensive, but in a market where there are a ton of options, price is a negotiation point.
- Better integrations with vendor/partners using the same tool would help onboard offshore resources we occasionally use.
roll-out of Salesforce when we were starting with nothing. It helped us manage
the scale of the implementation and keep track of resources. The user stories
you can create help to make manageable bite-sized workloads out of larger
multi-people and multi-month tasks.
- It has a lot of flexibility in the way you can create swimlanes, flag cards, and move things around on the board.
- Easy to track and follow your team's progress and see if you are getting things done according to schedule.
- The circles that represent the days along the bottom of each card are nice so that you can see if anything is getting stale.
- It needs a better way to auto refresh. Having to refresh the page sometimes can be frustrating.
- Sometimes it's very slow to reflect that you are dragging things between columns, and before you know it you have grabbed the wrong card.
Jira Software Scorecard Summary
About Jira Software
Jira Software is a software development tool used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects from a single tool, helping teams release higher quality software, faster.
And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- Easily re-prioritize user stories and bugs
- Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
- Estimate, track and report on story points; become more accurate
- Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
- Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
- Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
- Flexibly tailor Jira tasks and their workflows to a specific team's use case
- Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default
Jira Software Integrations
Jira Software Competitors
- Has featureFree Trial Available?Yes
- Has featureFree or Freemium Version Available?Yes
- Does not have featurePremium Consulting/Integration Services Available?No
- Entry-level set up fee?No
Jira Software Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Mac|
|Mobile Application:||Apple iOS, Android|