Jira is a Saviour
Jira Software is a project management tool that is widely used by various teams in our organization to manage their projects and tasks. …
Starting at $81.85 per month 10 users
View PricingOverview
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Standard
$8.15
Cloud
per month per user (minimum 10)
Premium
$16
Cloud
per month per user (minimum 10)
Data Center
$44,000
On Premise
per year 500 users
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.atlassian.com/software/jira…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $81.85 per month 10 users
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
YouTube
The full overview: Roadmaps in Jira Software
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a project management tool software 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. 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.
Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- 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 Videos
Jira in a Nutshell Demo Video
Jira Software is a software development project management tool of sorts, that tracks progress, offers up project reports, and gives a great roadmap view to understand workloads and deadlines better. In this video, the TrustRadius team goes over Jira Software pricing, top feat...
Show More Jira Software Integrations
Jira Software Competitors
Jira Software Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Mac |
| Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Jira Software starts at $81.85.
Reviewers rate Support Rating highest, with a score of 8.8.
The most common users of Jira Software are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(3243)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Pros
- Cons
Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.
Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.
Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.
Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.
Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.
Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.
Attribute Ratings
Reviews
(126-150 of 187)Companies can't remove reviews or game the system. Here's why
We use JIRA in many different implementations across our organization. We've customized boards for teams in our department to match their individual needs and requirements. With our teams using agile methodologies, we need the tracking software we use to be extremely easy to change and customize. No two teams have the exact same requirements or workflows they want to use and JIRA allows us to match the software to the team and not the other way around.
- Allows us to customize our board to match the teams' workflows and not the other way around.
- Allows transparency to management and other interested parties.
- If used appropriately it can help cut down on process bloat.
- It can be complicated to set up and manage. Depending on the size of your organization it could require a full time administrator to manage.
November 22, 2017
Review On Jira
We use JIRA extensively within the team as well as other teams. Particularly it's a bridge between the dev team, release team, network team and database teams and many more.
It covers all the dev modules and covers the implementation of code developed by the dev team in other production and non- production teams. It's the primary tool in our organization for end to end deployments of new components/fixes etc., into production.
It covers all the dev modules and covers the implementation of code developed by the dev team in other production and non- production teams. It's the primary tool in our organization for end to end deployments of new components/fixes etc., into production.
- The release engineer team uses the details of components that are to be deployed
- The performance team uses the tasks that have to be tested under load
- The network team implements i-rules and and firewall requests etc.
- It needs more robustness
- Cross platform portability
- More user-friendly
October 31, 2017
Great organization once figured out; very happy with them
It's used within the dev team (and by VP Product) only for Organizing product/dev ideas, stories, and sprints.
- The breakdown from "epics" (very high-level ideas, goals) into "stories", "tasks", and "sub tasks" is not only a project manager's dream, but really helps keep the company informed about what general things are being worked on and "how much more" there is to getting something accomplished.
- Love the Slack integration (keeping everyone posted on what just happened).
- The boards (and which ones people are looking at / which tickets they pull or don't) can be a little confusing at time. That's really my only con.
October 26, 2017
Judging JIRA Software
We use JIRA as our primary development tool for bug tracking as well as for Agile process management. Combined with Confluence, nearly all of our SDLC is managed within JIRA and Confluence (the latter being an extension of JIRA for documentation that is longer than convenient to fit into a single ticket). This tool is used primarily by engineering and product, but users in marketing and design also participate too.
- It is a well-known and recognized issue tracking tool.
- It is extremely customizable, both in terms of customization of the tickets themselves as well as how one can apply workflows to manage your process.
- Given its wide usage in the market, there are a number of 3rd party plugins/integrations available for JIRA; you can tie it to your repository and have an integrated view of development within the issue tracking tool (for example).
- Atlassian recently made a number of UI changes to both JIRA and Confluence. The Confluence changes negatively impact productivity by hampering what used to be a relatively straightforward navigation process. JIRA received an analogous set of changes; while less egregious, I find the new look increases my eye strain when trying to find needed information. New users may not have as much difficulty, but you should try it for yourself.
- Atlassian offers both a Cloud and on-premise solution; the Cloud version doesn't offer many customizations and plugins that are present on the on-prem (server) version.
- The amount of customization offered by JIRA is a blessing and a curse. Generally speaking, it's important to keep things as simple as possible; avoid adding custom fields or super involved workflows as much as possible (though the default workflow doesn't work in most situations based upon my experience).
- You'll need to nominate someone in your organization to own the JIRA effort -- this person should have a reasonable knowledge of JIRA administration but also have the ability to fairly present options and solutions as issues arise. If you don't have someone in this org but opt for a committee of sorts your instance can become a true mess and will negatively impact productivity.
October 24, 2017
JIRA is the only support tool for Atlassian Confluence users
JIRA was used to document differences between a desired specification and a delivered prototype. The organization being small, it was used by everyone. It was intended to be a single tool to characterize issue reports, compile bugs, author work orders & track progress for a web-based application tracking various aspects of building management & efficiencies.
- Integrates well with Atlassian's other products including Confluence wiki - this is essential since there are always reports, research & knowledge outside the scope of the bug reporting or support tool, and a general purpose wiki is absolutely necessary to compile this effectively.
- Produces reports about a particular release's deficiencies, when those can be characterized well enough by reporting users - essentially serving as a link between support people & developers, which is central to support-driven development, and necessary for DevOps integration between developers and sysops (where those are different people, which in a successful org, they would be)..
- Exports data well enough to standard output formats & notification systems.
- JIRA is part of a silo with Atlassian's other tools, like Confluence wiki. Just as Microsoft tools integrate tightly with its Sharepoint knowledge base (it's not a "wiki" in my opinion), Atlassian's form a stack that essentially requires one to use Confluence. Meanwhile if you are using the far more common & supported MediaWiki, you will find that for various reasons it is wiser to use Phabricator, the Facebook/WikiMediaFoundation bug reporting tool (competitor to JIRA) since the largest users of PHP-based mediawiki are also using that, and integrate them more over time. If JIRA wishes to compete for users who are relying on SharePoint & MediaWiki, who very much outnumber Confluence users, it will have to support those knowledge management / CMS / wiki systems as peers, and will have to restrict the degree to which it favors Confluence else it will be too great a business risk to rely on JIRA when using a non-Atlassian CMS or wiki.
- JIRA does not provide much direct support for support-driven development (SDD); that is, when one is specifying a new product entirely, with desired (not real yet) fictional features, JIRA would have some trouble characterizing this correctly. Yet for SDD it's critical to be able to represent a specification of desired behavior even when there is no running code that attempts to implement it, else there will always be a gap between a specifying tool and a support tool. JIRA developers would have to make a conscious decision to support "revision 0" of software; that is, its specification without any working artifact, and with only proposed URIs or command verbs, keeping these mutable so that potential support problems were found in the specification stage, and there was NO gap between tools used for revision 0 versus revision 0.1 to 0.9 to 1.0, only a difference in audience.
- Mobile & responsive support is weak - when a problem is reported it should be relatively easy to filter who gets which reports, and those should be sent through confidential means like XMPP or Signal, rather than relying on proprietary services such as social media (major security problem).
September 27, 2017
Judging JIRA
Almost every department is using JIRA. It is keeping our teams focused and providing better visibility to team leads. It also allows for rigid workflows so steps are not missed.
- Documented and rigid workflows.
- Automation where needed.
- High-level dashboards for management review.
- It is easy to use. This is evident by our high adoption rate.
- JIRA always has a snapshot of today, but it's hard to get trends.
- The marketplace has a lot of plugins, but most are not free. To build the best solution you may need to purchase several add-ons.
- Because it is very customizable you can end up with too many statuses or fields that mean the same thing. You need a good admin to help shepherd departments down the same path.
September 18, 2017
JIRA for Ops
JIRA is very useful to record and track requirements for small applications and records that we build. The tool is comprehensive, manageable, and provides good reporting. It also helps in tracking tasks and time management.
- Tracking multiple types of items under one roof
- Notifications
- Reports
- More organised way to represent requirements
- Better traceability
- Approval workflow
September 07, 2017
JIRA - I like it so much!
JIRA is used as a test management/tracking tool in our organization. It is being used across the whole organization
- Defect tracking
- Instant e-mail notification to users - based on the role they play in the organization
- Workspace creation to help teams managing their work inside a bigger projects
- Wish JIRA had more integration features with HipChat/other IMs used by businesses
- JIRA integration with HP ALM - this helps multiple teams using different test management tools within the same organization
- More intuitive burndown charts
June 23, 2017
JIRA modern tool for Project Management
Currently, we use JIRA in the IT department. It is very effective and efficient to manage our Agile projects. The task assignment, task progress, and workflow customization features are more helpful. The Kanban view technology is a virtual scrum wall for our team. It summarizes the status of the iteration in a single view and progressing tasks with drag and drop features is awesome. Integration of JIRA with GIT and Jenkin made our life lot easier. JIRA has definitely been a productive tool for project management and delivery.
- Kanban provides a summary of all stories and status in a single view. Easy to track the iteration and easy to progress the stories. It's like a virtual agile wall.
- Integration with Git. We can see all the code changed for a particular story and defect fixes.
- Integration with Jenkins to progress the status of story.
- I like everything about this product,
March 30, 2017
A nice tool for big companies but it's better to find an alternative for small businesses.
I use it only with website developers in order to describe what bugs need to be fixed, implement new features on current projects or to start new projects.
- Inform people by email that they have a new task or replies to their comments.
- Clear interface.
- Nice tool to update information, modify or add [info]. You can also attach files up to 5 MB or more according to your settings.
- You can use the self-hosted version or use it on your own server.
- It's hard to create new workflow schemes and apply them to some projects (not intuitive).
- If you want to hide tickets from people who are not concerned (add view restrictions), it's a pain. I had to contact support to set it up correctly.
- Pages loading are slow on the self-hosted version. It may due to sharing of resources across all customers.
March 20, 2017
Very few issues with managing issues
JIRA is used by R&D in order to work on adding features and improvements, as well as identifying and repairing bugs. JIRA is also used by engineering for working on server and data center issues. Lastly, JIRA is used by application support at a tier 2 and tier 3 level for troubleshooting single user issues.
- Creating dashboards for issue tracking and management.
- Highly customizable and many plugins are available.
- Logging, tracking and updating issues via email.
- Useful for project management but not flexible enough to effectively use for other purposes.
- The search function is poor.
- Interface is not terribly user-friendly.
March 07, 2017
JIRA is the way to go for Agile development teams
Score 9 out of 10
Vetted Review
Verified User
JIRA is being used across the whole organization as a bug and features tracking tool. We use the Agile boards a lot. During our sprints, we have each team assigned a board, where they can admit issues and evolve them according to a specific preconfigured workflow, depending on issue type (bug, feature, hotfix, etc.). It's easy to use and a key software to track a development team's progress.
- Share information across development team
- Track progress of development
- Manage Agile Boards
- Integration with Stash
- Better use of time estimation regarding Epics
- More graphics options
- Timesheet functionality
February 16, 2017
My JIRA Experience
We use Jira to help prioritize projects in our development pipeline. We also keep track of work that is getting done and at what stage of the project that work is currently at. In particular, it helps solve the business problem of letting stakeholders know when to expect projects to be complete and to hold third party developers accountable.
- Shows you data on all the tasks you have going on like time estimated vs. logged vs. left to complete.
- Helps you prioritize tasks and assign to different developers.
- Can organize your tasks and projects into smaller chunks that are easier to understand.
- Jira's graphs and charts are not super intuitive to set up to get sophisticated analyses on pain points in the project life cycle.
- Some features like filtering require a bit of tech savvy knowledge to use fully.
December 05, 2016
Jira is the last software tool you'll need for Agile development
JIRA is being used by our department for agile development and bug tracking, specifically Scrum. It is being used throughout the organization and it really helps with the transparency of the development cycle.
- JIRA helps the team share information and engage others seamlessly.
- Enables teams to work together with colleagues using joint-editing tools and monitoring the team’s progress and updates of each task.
- JIRA boasts a feature-rich service desk implementation that allows each department to collect customer requests instantly, and arrange them in priority queues that improve the productivity of the team and happiness of customers.
- Jira is very good at helping us manage small, executable development tasks, but it does not meet the need of understanding the full scope of an “Epic” (big project).
November 18, 2016
JIRA - For better productivity
We use JIRA for defect management and triaging.
- Creating defects.
- Tracking defects.
- Organizing defect items and helping in triaging them effectively.
- Integration with other similar tool suites like the IBM/Rational suite.
November 03, 2016
Jira: Swiss Army Knife of Agile Sprint tools.
We are using Jira across our agile office's sprint teams. Jira provides a collaboration model and workflow for developers, QA testers, and architects. Jira addresses our business's need for transparency: supporting the SCRUM framework of time-boxed sprint deliveries and supporting the IT department's production releases.
- Jira provides ease of use issue entry and workflow to developers, testers and architects. The Plan view works great for estimating and grooming sessions. The Work board allows full collaboration for the team's Stand Ups.
- Jira's sprint report area offers a daily view of burndown chart, sprint report, epic report, etc.
- Jira's filters and gadgets in the non-agile build are built-in. I use them every morning to create a daily dashboard. The Pie charts gadgets of Status and Assignee are clickable to the pie wedge, moving you right to the story or bug. Very cool!
- Jira could provide a Favorites list of recently used gadget/filter combinations when creating a new dashboard.
- Jira could provide a url link to Atlassian forums or Jira blogs that updates when opening the application.
- Jira could provide a history drop in the quick search field of the Plan view to help find that hidden story or bug quickly.
We use Jira to manage projects and support tickets in Engineering. It has touch points with Product Management, Customer Success, and Research, but it's primarily an Engineering project management tool.
- Jira's Kanban boards are easy to use and customize.
- The option to write your own queries gives you lots of flexibility for how your organize and display the workflow.
- Jira itself has a lot of traction in the market, so it integrates with a lots of other tools.
- Jira can be overly complex to customize to the way you need it. The administrative interface has become too complex. I've found myself stuck fixing something I'd really rather not spend time on more than a few times. Some of the concepts like workflows, screens, etc. have to be re-read every time you need to fix or customize something. This comes up often with integrations, where a field simply won't sync because it wasn't configured the right way. I let one of our integrations generate an error message for a couple of months just because I didn't have the time to fix it.
- Jira was designed as a Project Management tool and generally doesn't work for Product Management. For Product Management, you'll want a tool that can manage multi-product backlogs, user feedback, prioritization schemes, capacity planning and tradeoffs, and roadmaps.
September 20, 2016
JIRA - Love at First Site for Developers, a Slow Courtship for Business
The use of JIRA is company-wide but sporadically. JIRA is viewed as an "opt-in" tool in our organization and is mainly sought by the development groups. We have had some success pushing it out to business users in departments that would benefit from ticketing and tracking of workload. In general, development and QA are the primary users.
- Differentiated workflows. It was important to us that new product development could be handled differently than IT implementation bugs, etc., and JIRA does a great job of allowing us to treat efforts appropriately without a lot of complicating customization.
- Card view. The layout of the work items on the board is user friendly and easily gives the team a handle on what is happening during the working period. The drag and drop functionality is constantly lauded by our teams and whenever alternate tools are reviewed, is one of the top features used for comparison.
- Simplified Querying. One of the biggest selling points to the business groups that have taken on JIRA is that finding items in the system doesn't depend on someone with say, SQL talents. Though there are complaints on querying more complicated information from some, overall the WYSIWYG interface for querying tickets is very helpful for business users to "self-service" information.
- Integration with wiki tool (Confluence). This I think is one of the biggest draws for us on the business side. We find that JIRA is sometimes too complicated for the business user and were able to build dashboards and pages that help the business users navigate to what they need to know. Being able to maintain up-to-date reporting from JIRA without having to constantly update is beyond valuable.
- Reporting. JIRA has always been a little finicky on the reporting side in my opinion. The gadgets are helpful but can be confusing if you aren't shown how to use them. Time tracking continues to get worse rather than better with the removal of the one built-in timesheet we had replaced by a paid plugin with fewer options.
- Roles Based Permissions. JIRA is really light on this but you can work it out using validations in the workflows and permission schemes. I think this is not intuitive for most admins and they wind up with a very unrestricted instance of the tool. Sometimes setup can be a pain because of the openness.
- Ramp up is long. JIRA is really difficult to understand and to be properly configured if it doesn’t suit you out of the box. Once you understand all the ins and outs of the setup process you can wind up with a decent tool but it's the fact that you need someone to sit there and learn it before you can use it - not a coherent message to management when pitching Agile.
- Or to some "missing features". Some features that the community feels should be a part of the core product are only available via plugin. Again, the message to management when trying to purchase these is disconcerting to leaders that are used to the "big box, all in one, everything you need, one price" solutions.
- Business Features. Depending on your final configuration you may find tracking business features rather onerous. Based on release structure we have a non-traditional setup where our business projects exist in one space with children work in software spaces. It is the easiest solution to our technical release issues. There is only one ticket type that can have children spanning projects and it is the Epic. Pulling in children tickets is time-consuming and laborious. I discovered that I could automate update of a ticket field on children tickets to help tracking back but it's not elegant and is open to creating gaps should things change (and they often do in Cloud JIRA).
August 02, 2016
JIRA - The Godzilla of bug tracking softwares
JIRA is the main bug-tracking/requirement software used by my company. QA uses it to document bugs and keep track of the progress of a project. They also use it to report results to persons outside the team by using issue tracking Dashboards. Developers use it to set tasks for themselves and monitor their progress. Product uses it to set up Requirement tickets and define scope of project.
- The software is user friendly and there is almost no learning curve with this.
- The software is ubiquitous enough where most people that are hired have already used it before and so there is not much need for extensive training on it.
- There is enough flexibility while writing an issue to customize the bugs/tasks/stories based on the type of project it belongs to.
- There are a lot of ways to effectively track issues using different labels/customized fields etc.
- It is easy to set up a workflow in a project.
- The advanced search option is extremely helpful and flexible.
- The permissions for users are pretty hard to navigate through. The permissions controls are not user friendly and easy to understand or implement.
- There need to be more gadgets added to the Dashboard feature to make it more diverse and useful. Especially a text gadget should be a default option available and not an add on.
- There is no way to effectively sort tickets linked to one ticket.
August 01, 2016
Powerful and flexible - but not for the faint of heart!
It is used by our delivery, creative and technical teams.
It addresses the need for contextual commenting and feedback on user stories and bugs. It also is used to plan sprints, manage development work through the team and to provide constant feedback on progress.
It addresses the need for contextual commenting and feedback on user stories and bugs. It also is used to plan sprints, manage development work through the team and to provide constant feedback on progress.
- Highly customisable
- Constantly being updated and improved
- Flexible in terms of being able to adapt it to a number of different scenarios, e.g. Agile Project, Support Project, Issue Log, etc.
- It's relatively simple to use once configured by an expert
- Sometimes it appears overly complex, like it's trying to be all things to all teams - this can put some users off
- It was never built from the ground up as an agile software development took like Mingle or Target Process, sometimes this shows.
July 29, 2016
JIRA is a Japanese word (gojira)
JIRA was used to track the production cycle of thousands of internal digital products and requests. It was linked with Smartsheet for easy access to our internal database and helped with visibility across multiple teams.
- Organizes queues well
- Easy to learn
- Links with other software tools like Smartsheet
- Customizable
- A lot of manual entry in the beginning but administrators can create templates
- Since it's cloud based, we experienced a lot of system failures where we couldn't access information
- Could be very slow depending on connectivity issues
July 29, 2016
Jira is great for what it's good at!
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.
July 22, 2016
JIRA Software review
Since the company I belong to is working on Agile, JIRA is used for the following purposes:
1. Create tasks, epics, stores and requirements for different projects.
2. Reports issues.
3. Create deployment tickets.
4. Maintain Agile sprints.
5. Integrate with TestRail application for test planning and execution.
6. Prioritize tasks and maintain reasonable backlogs.
7. Update documents and make timing follow ups.
1. Create tasks, epics, stores and requirements for different projects.
2. Reports issues.
3. Create deployment tickets.
4. Maintain Agile sprints.
5. Integrate with TestRail application for test planning and execution.
6. Prioritize tasks and maintain reasonable backlogs.
7. Update documents and make timing follow ups.
- JIRA is a very good planning tool.
- JIRA is a very good issues reporting tool.
- For me it's pretty convenient.
July 20, 2016
Getting projects done fast
I used JIRA Software for a client organization in 2015 to manage various tasks across projects. It's useful in managing git commits and keeping everyone in the loop as far as what needs to be done in each project. Various users can review and/or add their comments and look at the branches to ensure the work is getting done. It also allows for time-tracking on the different tasks and estimating time as well.
- Time tracking
- Project/task setup
- Git integration
- Confusing interface. They need to clean up the interface a bit.
April 27, 2016
JIRA, at the forefront of the industry.
We use JIRA in conjunction with our partner. During our prototype design phase we use it to track any issues encountered by either party. It is also used during a products life cycle should any problems be found by customers or if redesigns are necessary. JIRA is used exclusively by one department in our company. It addresses the need for transparency and communication between the necessary developers.
- Issue tracking.
- Project management.
- Variable workflows.
- High learning curve.
- Not viable for certain types of development.
- "Clunky" user interface.