In a few words JIRA is a task tracking software that makes life easier when working on a project.
Once the initial setup is in place (easy to do for common scenarios ) all is left for an administrator is to manage the list of projects and user accounts.
Note that parts of the process (e.g.: customizing workflows) need to be done up-front, since this will become more complex once one or more projects are configured and in-use
As for usability, it is one of the best tracking systems I've ever used: as a developer/QA you can easily update the status of your work in a user-friendly way. As a manager, you can always get the overview you need by just opening a screen or a report (most of what you need is in place by default)
What's best about it is that as long as it is installed on-premises, it can be used as a central point of information for everyone involved with a project. The fact that it can be integrated with other common software industry tools adds further benefit from this.
In the end, I should probably add that I've been using all kinds of bug tracking systems for about 15 years (starting with ancient tools like redmine going through PivotalTracker or VersionOne or JIRA) and almost all of them were either missing features that I deemed important or "spartan" usage/layouts that constraint the usage.
JIRA just provides everything that's needed in completing a project out-of-the-box (whether it's Agile, Waterfall or Kanban or whatnot)
- Overviews & quick access to information
- Possibility to integrate with most commonly used systems (it integrates with pretty much all mainstream tools, nut just the ones from Atlassian) - you can integrate it even with continuous integration tools or test management tools (e.g. TestRails)
- Security control (everything is fine grained, tools to configure fine-grain access are already integrated
- Comes out of the box with the most common work scenarios (client onside/offsite, development only/development + product management, etc)
- Reporting (easy to extract the things that matter (whether this is worked hours or development velocity)
- Version management (easy to manage what features are grouped in a release, or what fixtures were done for which version)
- Workflows can be customized to match just about any real-life usage scenario
- Allows for both on-premises (self-hosted) installation and cloud usage.
- Configurable dashboards
- Pricing - it is prohibitively expensive for small companies, although they are making steps to minimize this with the new pricing models (e.g.: a few years ago they started allowing up to 5 accounts per project and unlimited projects, for a fixed yearly fee).
JIRA is easy to use and great for managing work tasks on a project, however customization options are often only available to admins.
Our company uses JIRA to manage work tasks. It has all the important features for assigning work to team members, tracking how long each task takes, notifications, capturing comments and hours worked. The tools allows for the flexibility to create your own JIRA ticket types or categories, with any kind of number of input fields. Data fields may be dropdown boxes, tags, values, or free text. Fields inherently have the ability to recognize hyperlinks and add those in once you type out a link, and it also recognizes JIRA links, such that if you enter a JIRA ID tag, it automatically creates a hyperlink to that JIRA entry. JIRA supports Agile development schemes and tickets could be easily tracked through a JIRA Dashboard. JIRA filters are also easy to use. You may use the basic query that provides you with simple dropdown fields for common elements, or you can create more advanced queries using JQL.
Being a JIRA user can be limiting as you only have the ability to enter data for the fields that are currently configured. You have to go through IT or the admins for any form of customization such as adding/removing/hiding fields, setting what kind of text format is in each field (e.g. plain text vs rich text) and modifying which fields are required vs optional. When you have rich text formatting, sometimes it can be frustrating getting the text to show up the way you want. The workaround for this would be to use the Text tab instead of the Visual tab so that you can modify the formatting tags.
Jira surprised me as coming across simple yet being incredibly powerful and versatile. It is a full blown Ticket and workflow management tool and it might be too much for small or personal projects. However, not being required to change the ticket system when the company or the team scales or are faced with types of tasks you did not expect is simply fantastic. Keeping software simple, easy to use yet increase its versatility and power is a virtue and Jira is build upon this virtue with care and vision
Jira is clean and it is simple yet powerful. You can use it for your basic ticket workflows from the get go and expand as you grow or the tasks you wisch to cover branch out. It is easy to customize the ticket views to contain the information you want to use and avoid cluttering. The Workflow editor is one of the most powerful I came across in all my professional career. It might not seem so much of an importance but believe me, when your business grows unexpected necessities will arise and you will suddenly be required to track tasks you never though about. Jira will have you covered and allow you to add different task types which traverse task-type specific phases and have corresponding stati. Also you have all the world of notification and responsibility tracking ping-pong covered as you go. Two further things are woth mentioning: First the Atlassian World (the Wiki Confluence and build system Bamboo and many other products) integrate flawlessly and it actually really makes using them fun. Jira is one of the tools, that make you smile when you are required to use it no matter the task to track, its jus smooth, convenient and above and beyond provides a rich ecosystem for free and commercial plugins even for rather exotic use cases.
Also, the license Model behind it scales fantastically. When we introduced it we were a small company with 8 people (we are now going strong towards the 200) and it was critical to keep cost for our tools reasonable. Jira got us covered.
When we scaled, the License was not as flexible in higher user tiers as it was in the lower ones. Also once upon a time an update went wrong and we had to invest a bucketload of time and brain power to get everything back up to speed. We did run jira on premise and hat some custom plugins so there might be some of the tripwires: In case you use plugins they must be available in the version you wish to upgrade to and this might require some research prior to updates. Also, you can make a science out of the workflow and notification configuration. In case it is not documented well when you do it it might get you into trouble.
We are able to use JIRA to create, collaborate, test and deploy promos and emails for my company. I am able to see conversations and other notes from people I don't normally interact with, which can be really helpful in understanding issues that arise or other notes that may have been left out of conversation elsewhere. It's a great tool for us.
I work for a large clothing retailer that often runs promotional coupons and sends out emails to customers. JIRA houses all of the collaboration for our company in creating and testing these promos and emails. What I like is that everyone, from the communications team to the Quality Assurance Team to the IT troubleshooting team can be in one place to resolve issues quickly.
I love that there is the ability to tag other users and quickly get attention to issues that need a fast turnaround (emails and promos are often made within 48 hours from creation to launch). I also really like attaching 'sub-tasks' to a main project; This keeps organization a priority without having to search for every related task associated with a project. Related to this is the ability to attach documents right to any project/task for easy download.
You can save searches and filters to your home page. For example, I have a filter for viewing only email projects, and another for promotional information. Once you get results, you can sort by title, date updated and a few other categories.
At first glance, the layout is a bit overwhelming. You have a giant list of projects, and the search doesn't always bring up what you are looking for. It takes a bit of time to learn how to navigate. I would probably like to see 'tags,' or additional ways to categorize a project so that you can search for it through a few more parameters. For my needs, this isn't too important because of the short lifespan of emails and promos. But I could see other applications needing something like that.
JIRA has lots of features and functionalities than can take time to master. From most project management applications' perspective, JIRA is one of the most complex to master. But it truly is the most complete in terms of offering development teams all the tools they need. This means that trying to run a fairly large and complex enterprise environment on JIRA might need the addition of a JIRA administrator to keep things organized.
JIRA offers true Agile support for managing technical projects. Initially developed by developers for developers, JIRA is a powerful tool that captures more than just the project management aspect of any development project.
JIRA offers a complete suite of issue tracking throughout the development life cycle. Starting with the backlog and planning, JIRA lets you layout your entire project across as many iterations (Sprints) as necessary. It provides ease of tracking the project progress and offers a host of tools for collaboration such as commenting threads. Projects and their projects can also be tracked across releases, with its release management capabilities, and provide comprehensive reports on performance and progress.
JIRA is extremely flexible and offers pre-set templates across all functionalities, and allows you to modify them as neededto fit your team and organization's needs. Unlike some products with rigidity built into them, JIRA allows you to define how your team works.
JIRA has a vast number of integrations and add-ons to further enhance its capabilities.
JIRA is very powerful and very detailed. So much so, that some users often find it quite cumbersome if their development environments are not complex. Essentially, JIRA fits beautifully in any environment, but is extremely robust for enterprise environments, making it perceptively complex in small simple projects.
Currently, my organization is moving from waterfall model to Agile model (hybrid), JIRA has helped a lot to standardize the reporting of granular project details to be reported as a consolidated approach as to how the sprints within a project are moving forward.
JIRA has given the transparent view of how the projects/sprints for a product is moving forward and managing the interdependencies within a project.
- Manage multiple projects under one project in JIRA and works well for a complete program
- Email notification when any changes made in JIRA makes collaboration efficient
- JIRA board (Scrum Board) in JIRA and defining specific project JQL to filter the issues in JIRA makes it more user friendly for scrum masters who are managing multiple scrum teams in a program
- Automated dashboard creation and ability to create different charts makes it very easy for showing management rpeorting on different scrum teams progress in a sprint
- Sprint and version reports (out of the box) which provides burn down charts and which issues are lying in one state for more than a specific period of time helps scrum team to move forward and resolves impending issues
- Ability to link issues for dependency and flexibility to define SDLC life cycle for an issue on a board makes it very handy on any type of project
- No single view is available to see clearly how dependencies are moving forward
- There are times when single issue has to be given to multiple people like in pair programming one way is to create sub task but that is not an approach that was liked by scrum teams
- There macros / gadgets that comes with the JIRA product are very minimum they should add more gadgest for reporting purpose.
- Yes, there are different third party gadgets but sometimes those are not JIRA / atlassian recognized and for enterprise application and corporates using JIRA does not go ahead to deploy those third part gadgets on the server model.
It's been a great experience using this tool for me
As a business analyst, I have been using Jira for last 3 years and I think it's the best software management tool around.
I have found it really helpful when it comes to providing upgrades to the projector to administer a project in development stages. It's all in one package.
It has the board where you can re-protize your user stories in backlog by shuffling through pick and drop feature for the development team through tasks as well as can prioritize issues reported by the customer. You can write the user stories and just need to manage on the board. You just need to monitor the board to track the progress of the critical item and estimate overall progress.
Workflow templates are available that can be selected to select the process a team wishes to follow or a path to take to address the release or apply patches on customer system. You can add the workflow by create one in the system and add the additional steps like unit testing, system testing etc as per the team.
Another helpful feature that I love about this tool is that I allows integration with multiple other tools that makes it even better. Overall I think it's a remarkable tool that is making the software handling experience easy and simple.
The only thing that I hate about this tool from atlastian is that it have a lot of the patches applied and part of constant changes. We need to scratch for sometime when configuration have to be modified or any existing thing changed.
It takes for a while to get your hand adjusted on the system but when are down it's always good experience using it
Jira is a task administration programming that is very mainstream among numerous organizations. With an extremely high score of 9.4/10 and client fulfillment at 99% it is as of now one of the best 3 best task administration arrangements looked into on our site. The primary spot in this class is held by Wrike which has an aggregate score of 9.8/10 and is the champ of our Best Project Management Software Award for 2017. You can experiment with Wrike for nothing here. You can likewise contrast Jira and Wrike and see which one is better for your organization.
Jira is intended to enable clients to catch, dole out, and set needs to their work. It enables you to deal with the entire procedure of use improvement ensuring that everything is secured, from idea to dispatch. Its straightforward, natural interface empowers joint effort with partners and enables you to take care of business in a viable way.
Jira tailors itself to fit to the necessities of the business and gives fantastic help to finish everything. The level of customization enables the product to properly fit distinctive business needs.
This product can be utilized by an organization. I have designed JIRA to be utilized by distributing organization, by law office, and obviously, IT organizations. What's more, it was conceivable to make everybody content with what JIRA gives. Despite the fact that occasionally it was difficult to encourage individuals how to utilize it, following multi month or two they couldn't recollect how they lived without it.
Jira is an amazing programming, however with a lot of capacities comes a large group of devices and assignments to learn, especially for new clients.
As of late JIRA refreshed its outline. My clients whine about new outline, I get insane when I can't discover things. Furthermore, JIRA wouldn't like to stop at that and is refreshing its plan further and further. I would truly incline toward that they glance through bugs that were raised on comunity entryway and accomplish something in regards to new highlights as opposed to doing configuration refreshes.
It is imperative to realize that Jira gives us awesome help to the client, and their consideration is a need, however ordinarily they don't figure the issue. It is a component to survey in Atlassian.
- The prologue to Jira's reality is required to be as mysterious as its interface and execution. Actually it is intricate to fabricate channels and move around in the application when the client is new.
- You need to run a right download of the reports toward the finish of the month or toward the finish of the week, the reports are conveyed in spreadsheets, however with an introduction that fails to impress anyone, thusly, when setting the dates they ought to have pretty much days so you can play out the download effectively.
This software helps us to follow the process the team agreed to, and see the progress on issue and sprint level. We manage several projects there.
JIRA by itself is a perfect solution for IT teams when it comes to managing projects. Not only you can create issues there, but also you can build workflow this issue goes through. It is perfect to see the bottlenecks of your process. Scrum and Kanban are supported. In case you need some enhancements, there is an add-on market available, where you can find a big amount of third part addons available, either paid or free. Paid once have a trial period during which you can see if this is really what you need for your business.
Along with JIRA we use other Atlassian products, such as Service Desk and Confluence. Easy integration with these, makes our daily job much easier.
I advice my customers to use JIRA for their business. There are several types available: Cloud and Server. Each one have their own payments depending on the size of the users. However, in some cases price might become an obstackle.
In my opinion, this application can become really helpful if it gets into right hands.
This software can be used by any type of company. I have configured JIRA to be used by publishing company, by law firm, and of course, IT companies. And it was possible to make everyone happy with what JIRA provides. Even though sometimes it was hard to teach people how to use it, after a month or two they could not remember how they lived without it.
Recently JIRA started to update its design. My users complain about new design, I get crazy when I can't find things. And JIRA doesn't want to stop at that and is updating its design further and further. I would really prefer that they look through bugs that were raised on comunity portal and do something regarding new features instead of doing design updates.
I am a technical writer who used JIRA as my first introduction into working in a close-knit, agile programming environment. I really appreciated the clean design, multiple ways to accomplish tasks, and logical visual representations of concepts. Is something assigned to you? It has your face on it. We had several development teams working in tandem and JIRA allowed for each team to structure their sprints according to their own preferences (some had more traditional set up and others used kanban). As time went on we were able to add more projects to JIRA, after transitioning off of ClearQuest for our baseline fixes, and while there is certainly a learning curve getting established programmers who have used one system of tracking for 10+ years converted to using JIRA, most everyone was able to transition and feel comfortable within a few weeks. Speaking as a non-programmer, I found JIRA to be incredibly useful and easy. Tracking writing and editing projects through development didn't require any specific setup or features and it was all around a great tool.
While it was great that every project could be tracked from our one JIRA site for my relatively small (30ish people) development team, any time fields needed to be added for one specific team to track something for stories or bugs, it was there for everyone. This led to having rather cluttered add screens that meant for a good deal of scrolling. I know some of this was surely user error, but having a bit more control would be nice. Also, the search function occasionally would just... not work. At all. As adorable as the sad faced little magnifying glass was when this happened, it would be very frustrating to lose functionality without warning. Being browser-based always makes for risk and some days would just be constant checking of if JIRA was up again so untracked progress didn't fall through the cracks.
A powerful, mature, and highly customizable Project Management software that works in any scenario. Best suited to match the dynamic nature of Agile projects.
As a Project Manager, we have a lot of things to do and think about. Good thing I stumbled upon JIRA. It is a very powerful and collaborative PM tool which supported my PM role in an Agile context. (I was on a standard/waterfall project methodology for years... Agile is rather new to me)
It is highly configurable, meant to suit any niche, industry, or user scenario by combining the powers of Kanban and Scrum. You can set up just about any of your workflows, project states, fields, action/issue items, etc, via the default settings (that surprisingly some have worked out of the box), or by easy customization on demand.
Data analysis is easy as well. JIRA collects from all data points you set up into a single data hub that is extractable, searchable, and comprehensive (with all your historical data).
The core program and its APIs are pretty mature and with proper documentation. Our devs didn't really have a hard time since they were provided with a rich toolkit to begin with.
JIRA also comes with its mobile app so that you can manage your projects on-the-go. It is cloud-based via subscription which relieves the admins from the difficult part of infra and server setup. I have not experienced any downtime as of my 1 year use of this service.
It is cloud-based so you have to make sure you have enough bandwidth provisions to support this (rather challenging for bigger teams working on the same location at the same time). The usual loading times may take longer with poor connectivity.
A rather steep price for small businesses to use. Self-hosting JIRA will also make things more expensive (and risky) as the number of users grow.
I have been working in information technology field for more than twelve years. For a long period, I was a big fan of Bugzilla. However in my previous company, when we have migrated to Atlassian Jira, it was a very difference experience.
When the entire organization moved more in to agile, the product also changed priorities around understanding customers' problems. The migration was tough as we were not in a position to ignore the requirements from our users. The import functionality helped us a lot and thanks to our engineering team to put huge effort in doing research on Jira.
I love the way information is organized across, projects, boards with decent agile reporting capabilities.
Being in product management, I have enjoyed the flow of user stories, backlog review, estimation, roadmap and Atlassian Jira's functionality to customize workflow.
The transparency which Jira brings to the product management team is a big plus. What we are working on, what is going to come next and when, what is in the pipeline are a big relief to any customer facing product development organization.
Another beauty is the categorization of user stories and epics, which helps the product owners to start filtration of issues at the entry level itself.
The knowledge handover from product team to other teams collaborating for product success ( Eg:- CS, Marketing) became seamless with Jira.
The dashboards are great for monitoring purpose.
Finding Jira, an effective and comprehensive solution to ensure that every action in a user story is accounted and traceable across the product life cycle without loosing the goal of delivering iterative and incremental value to customers, as fast as possible.
I like learning new things. Jira require good learning and is not a very light tool. The user interface act a bit confusing sometime. Setup, project/workflow creation, user management etc. are tough tasks and require brains from Dev ops with good knowledge of agile practices.
Jira helped us to more easily manage multiple teams of software developers and gather feedback from end users for several large applications that we were developing which were at various stages of completion and usability. We were able to use our available resources in a much more optimal and seamless manner, which helped us to complete projects and resolve issues more quickly, easily track the status of specific tasks across multiple projects/teams and monitor productivity at various levels. Ultimately, this allowed us to both reduce development costs and complete our projects more quickly which in-turn increased our business revenue.
Jira is a very powerful tool for managing teams of software developers working on one, or even multiple projects simultaneously. It is very robust and feature-rich, with features such as setting up/managing individual tasks, coordinating development efforts across tasks/developers to maximize team productivity, managing/tracking issues & bugs, gathering feedback from non-technical users via Jira user stories and managing project backlogs. There in also embedded support for Scrum & Kanban boards, although I haven't personally worked with those features. The custom workflows allow users to setup and manage their projects & teams according to the needs of their business and their preferred software development framework and management style. Jira is a very comprehensive, all-in-one tool for managing smaller teams of only a few people, all the way up to very large teams of 100+ stakeholders.
Given the robust features and functions that Jira supports, there's a lot of depth and breadth to the software, so it can be somewhat complex and confusing to newer users, especially those who haven't worked much with project management tools previously. For project managers who are leading multiple teams simultaneously, things can get a bit overwhelming because the email notifications and project alerts can quickly start to become excessive, and there's no way to consolidate notifications across projects/teams.
We are able to manage our internal approvals effectively. It is really helping to track the status and for expediting the approvals. It works even we are not connected to office network. You can simply connect if there is internet connection available. It helps us to complete cross border approvals easily and reduced manual work and hard copy print outs. It also reduces time for internal approvals and helps to manage even huge volume of internal approvals by the stakeholders. The resources need not run from one desk to the other desk.
This tool works on a hosted model and can be accessed from anywhere in the world by using internet connection. The web version and even the mobile version (which i guess has been recently launched) is good and can be accessed through click of a button while it is assigned to you. It is has various options like assigning to different users, obtaining their comments, attaching supporting documents, printing the ticket, reports and dashboards which can be customised by the users, option to download, link the ticket with other tickets, etc., The tool has the option to create various workflows as per the requirements of the users. It has the option to alert the users with email alerts and also reminder mails. There is option to close the ticket, clone the ticket, revoke the ticket. The users can customize the reports and dashboards as per their requirement and download the ticket in various formats from the JIRA tool.
The reports and dashboards does not provide for reports in a graphical way. The tickets can not be simultaneously assigned two or more users. The tickets can only be closed by the creator which is a set back if the creator does not close the ticket once its gets over. The note which is created allows only text inputs. It does not allow for creation of table or column. Turn around time for closure (at each specific user level) of the ticket can not be generated from the reports automatically. This is a big drawback. Also, it takes so much time for loading the contents and if the internet is slow then it does not get loaded at all.
Have a better control of the hours of each project to measure profitability
Have a clear picture of the hours executed by the collaborators, facilitating decision making when mapping a person in other activities.
Facilitate the online client that can see the progress of their requests
The power of the reports is very good
It has an integration with Power BI that we have not exploited yet but it will be the next steps.
Have an organization in the projects and services provided by the company to measure the profitability of them.
The reports modules to measure the speed of the work teams.
Have a detailed control by activity for the consumption of project hours
For cases of customer service, the power to share the information online and live consumption of hours and progress of the tickets generated to solve events.
The customization of fields to adapt them to the functionalities and requirements of the company.
The ease of creating reports based on the declared queries.
Make a general dashboard for the whole team and that the management line can edit, customize and share specific dashboards with different metrics.
The integration that you have with Project Server and Project Server Online of 365 facilitates the administration of projects and the record of hours per activity is reflected in both platforms by the time sheet
The addon to integrate project Server Online asks to deactivate the module of hours and in my current case is basically the corde of use. so we were willing to sacrifice integration hoping to have a response from the manufacturer that we can do to integrate Project Server Online.
If there are several admins and use different languages when one of them creates the types, subtypes or queries, the other user gets complicated when palicarlo because they are created in another language. example task - tarea
JIRA has helped us to organize our projects and keep them organized. Combined with the other atlassian products, we've streamlined how we document our work and stay organized. It's allowed us to do a variety of projects with different project management methodologies and workflows all within one software platform. It's also allowed a great deal of transparency into the development process for management which has greatly reduced the workload on project managers by automating some of the report generation necessary to show progress.
JIRA isn't perfect, but it's by far the best project management software I've worked with.
JIRA is ticketing and workflow management software. The things I like most about JIRA are how customizable workflows are, the availability of additional third party plugins, and how well it integrates with other atlassian products. The integration with other atlassian products improves our workflow significantly in IT and development, it allows us to link git commits through FishEye and documentation pages through Confluence to every JIRA issue.
JIRA's customized workflows also help us stay accountable to eachother. Because the workflows have specific permissions and assignees built into steps in what we do they help insure that the right person does the right thing at the right time. I don't think we could work without JIRA or something similar.
The software has gotten progressively slower over the last few revisions. That's my only complaint. The first load of JIRA in the mornings especially seems slow (About 20 seconds in the browser).
Keeping track of a Sprint, a project, a quarter or a year of work is easy. Working on an Agile team, JIRA makes my life better. It has all an Agile team needs to work together on the same or different features.
That they are constantly improving and releasing new features that make my life easier as a QA working on an Agile team. My team relies on this software of keep track of what we are doing. It has lots of nice features that we use such as to link issues to one another, link tickets, put labels of versions to be released, link to pull requests on Git Hub and scale priority and story points.
My team also uses a lot the Stories, creating Tasks under them. It's also nice that I receive emails whenever I am watching a ticket in specific to keep track of it.
My entire company uses JIRA across different boards and when you want to contact a team in specific it's easy to just open a ticket or link it to another.
As a QA I also use the filters a lot to find issues that are assigned to me or have been reported by me.
My team also creates boards separating them by Sprints. Which is a very easy feature to use, it considers the back log and it's pretty simple to have a Planning or Retrospective section looking at it. We're happy with the features that JIRA offers.
The person that organizes the board and tickets need to know a lot about the software to be able not to let it look messy. It's easy to create unnecessary tickets and put them on different places and end up losing track of it. Also, it's not easy to configure the boards to fill in correctly the burn down or any kind of chart.
I have enjoyed using Jira at work. It helps keep our team on the same page and gives insight into what everyone else is doing. My opinion is that they have hit the mark in a big way and they just have some cleanup/maintenance issues to take care of.
1) Jira is performing well in the industry which results in lots of people integrating with them. The most impactful for us was the integration done with Zenddesk our ticketing system. Our support engineers are able tie Zenddesk tickets to our Jira issues and when issues are updated, so is the Zenddesk ticket. Very Cool!
2) Notifications were very well done in Jira. There is an in-app notification system (A bell in the bottom corner) but they can also be sent via email. They also are very smart about sending you only updates that involve you so that you are not notified too much.
3) Smart task ordering and prioritizing that work well in a development environment.
Most of the cons that I noticed are rather nit-picky however I believe there is room for lots of improvement.
1) Give for example the sprint page. There is a little star in the upper right corner. If I hover over the star I get a description that says 'Star'. That is not a great description of what that button will do for me. Users are dumb and won't figure things like that out on their own.
2) I think the UI is a tiny bit clunky. I see lots of wasted space here and there. Often times there are things that do not seem that important that seem to take up a lot of space. Also I'm not a big fan of huge collapsable side menus.
3) The many features that are offered in Jira make for a steep learning curve.
I've used JIRA a few times, along with Confluence when I was on contract with a few large enterprise digital teams. I found JIRA to be excellent as a tool to share files, track project conversation streams, and manage multiple versions of files through the project lifecycle. Though I only ever used JIRA from an end user perspective, I always heard great things about the customizability (it seems to be a word) of the app to different business processes.
Digital teams, such as UX design, development and copywriting are an ideal use case for this app provided stories and projects are set up properly. It's a great way to give stakeholders and PMs and other managers visibility into how projects are trending against milestones.
There were a few outages when I used JIRA, but it was generally reliable. JIRA seems to be one of those business applications where you're only using a fraction of its capability. Administration access should really be restricted to a qualified few, as you don't want to have conflicting stories tracking the same project, telling different information.
The success of a JIRA implementation/adoption really relies on the quality of the data users, PMs, and development managers put into it. I found that I was writing a lot of updates and @ing people all over the place on one contract, yet certain PMs were still asking me for updates. That was less a JIRA problem, and more a condition of the people I was working with though, so I won't name names. :) - Moral of the story, you get out of JIRA what your teams put in, like many enterprise apps.
Scalability of our development teams was the biggest benefit, this product enabled us to grow and not lose productivity in the process. We were able to maintain good line of sight to what teams were producing and which ones were on track and which teams were off track. This invariably reduced the cost of our development, enabling us to grow faster and get product to market quicker in a highly competitive space.
JIRA gives you the essential tools to manage your development projects and comes into its own when you scale up managing larger teams and 100+ developers. User stories, epics, issue management, backlog management, task assignment, tracking charts for scrum, kanban boards etc give you the visibility you need when operating in an multi-team Agile development structure. The visibility of the state of your project(s) and workflow is the key benefit for using this software in an enterprise environment. Another key benefit is you can extend to use Atlassian's suite of products where there is great integration such as Service Desk, Confluence & Stride - although most of our teams eventually developed a preference for Slack.
JIRA can be a little complex at the outset to the uninitiated, some tasks require searching for in the menu system. Customization does have an overhead attached, for example adding attributes with logic etc. Email notifications can be overwhelming if you are attached to multiple teams, a digest option would probably be better than one email per update.
My Overall experience in JIRA is 3 years at this point and we started using it from the Year 2016. This is used in an project called recovery with the count of 25 developers from India/USA/Canada and several business end users on the same. The stiry was easily created and went thruough several phases till deployment. I would say JIRA ease my works in managing the stories since I am the PO for whole board and connecting developers/business end users for moving the stories and completing the same.
Basically there are lot of likes about this software:
1. Clear Tracking of what is going on in the project along with version needs to be deployed.
2. Ability to Use Kanban, Scrum and other Agile methodologies in JIRA Software.
3. Ability to flag the stories which is in impediment which will show to everyone on when it was started and when it was impended.
4. Easily keep tracking of Backlog for future works and deployments that needs to be made.
5. Ability to bulk update the stories for certain categories like version, points or any others.
6. Easy in terms of reporting to generate using JQL (JIRA query language).
Some of the cons in JIRA are:
1. Some times it was ended with deadlock leads to slowness. This happens when certain users running the report across the JIRA.
2. Security is less since we can see any ones board and get to know the statuses across the enterprise.
3. JIRA is costly since it per user licenses and whole organisation have to pay according to the usages.
It helps my team and my company keep track of all the features and bugs we are working on, and is a powerful project planning and organizational tool. The integrations with GitHub, Zendesk, and Power BI are incredibly valuable, and help automate much of our issue management.
Jira works incredibly well for large organizations, allowing each team to have their own workspace for projects, epics, user stories, and bug tracking.
It is incredibly flexible, allowing each team to customize the fields that appear on each issue. This lets the teams customize their workflows, and makes it possible to manage very diverse teams such as art, development, and marketing all within the same system.
It has very powerful integrations with tools like GitHub, ZenDesk, and Power BI, which helps automate issue tracking and provide organization-wide statistics and analysis.
Flat-fee pricing for small teams is very competitive for the amount of power it provides.
Way too much overhead to actually get started. Jira is so flexible that you have to invest a lot of time to get it working the way you want.
The layout of the interface isn't very intuitive and can take a lot of time to learn. They sacrifice usability for flexibility, which is a blessing and a curse.
This tool is far too complex for a small company or team, although it may be a good choice if the company is growing quickly or manages very diverse teams.
Greater organization in the planning of activities and approximation in the execution times of the development of each of them, together with the application of the agile methodologies implemented for the development of the project.
The dynamic structure to organize the activities and the income of the estimation of the execution times of each task, since it facilitates the application of agile methodologies in software development projects.
Jira also allows the inclusion of those responsible for the development of each activity, in addition to notifying the person in charge of supervising it, facilitating an early detection of impediments and / or progress during the course of the tasks that are carried out.
Also, the integration of Git provides valuable help when verifying changes in the development of the source code. It also has the possibility of sharing information through files of different length (.txt, .pdf, word, .mp4, among others) in order to provide greater ease of understanding to the person responsible for carrying out the informed task.
In addition, this tool offers precise search filters, saving time in the handling of the interface to focus on what the user wants to obtain.
1- The synchronization time of Git with Jira slows down with some internet connections, limiting the use of the benefits of this tool in some users.
2- The user has a lot of freedom to make changes in all the modules of the tasks. Although notification of the change should be a hierarchy of charges to perform them.
The tool has always done what I needed it to do and is very easy to use. It is clear and concise and helps my team focus on what needs to be done, provides the visibility to me and our customer where things stand and allows us to be transparent with the customer. First rate tool that is a must for any software team or entire project team.
I have been using the cloud version of JIRA for over 9 years. One of its best features is they keep expanding its capabilities and don't change the cost. Don't get me wrong the tool has always done what I expected it to do and done it well, but with each release the generally add some features and capabilities it did not have before.
I love that they allow Kanban boards and sprints on the same project - if that's how you want to work. Super flexible, fast and easy to use, even when I'm doing Admin work that I don't do everyday and can't remember exactly how to do it.
Additionally the tool has lots of add-ons - we use Tempo for time keeping and have used Gliffy in the past for diagramming. I'm not sure if
My least favorite thing is that they have changed the interface several times while I have been using it. However each time after I spend time getting used to it I find their redesign to be significantly better. I really find this when I use locally hosted older versions and see what I used to do - I really realize how they improved it.
We are using JIRA to manage our complex institution management system where we are following agile process. JIRA helps in managing and tracking task. If one has got good grasp of usinf this software It is a powerful tool. We use a feature Log Work of JIRA to lof our daily work on tasks and sub-tasks. JIRA is able to generate time sheets based on work logs. JIRA cab be customized based on one's particular need but It is bit harder to understand this feature. JIRA is not costly if the team size is less then or equal to 10.
JIRA is popular issue tracking and project management tool developed by Atlassian. JIRA has all advanced features a agile project management tool provide like scrum tracking, Sprint burndown chart, Agile reports, velocity charts. JIRA supports estimation of tasks in points as well as hours and does also rack the actual time spent on task. We have customized JIRA based on our project workflow like a sequence PO Review, Start Progress, Unit Testing, Code review, QA Testing, Done. JIRA Supports estimation and lifecycle of sub-tasks also.
Although JIRA supports all advanced features of agile project development but still there are some area of improvement in it. User has to make 2-3 click to edit task details. It is bit hard to understand the features of JIRA for beginners and for administrators. It can be very complex to customize to the way you need it. I found JIRA bit hard when i wanted to move multiple tickets from current sprint to next sprint.
If you stuck somewhere defining the workflow scheme in JIRA you would have to contact your senior or search for help on internet.