JIRA great for tracking and Assigning tasks

Pros

JIRA is currently the main platform for me at work. The entire faculty and college uses it for creating tasks, assigning tasks to others and tracking the progress of students. The IT department has tuned the JIRA in predefined certain way to meet the needs of our daily work so it shows that this software is very versatile and can be used in many different ways depending on the application. Sine everyone who is part of the team can access the pages we all can see the progress and there is a better visualisation of the project and progress. We have certain response teams created in JIRA so when there is any task created for a student and a proper response team is assigned all the team members get the email and updates which I think is pretty neat. I also like that i can add progress comments to track history and easily tag other people on it so there is transparency. The filtering on JIRA is something that was new to me and I thought it was a very nice way to unclutter that huge list of tasks on my front screen. The searches and how the different progress and roadmaps can be made separate should be used to make sure things are not getting mixed up. JIRA also has this unique feature where you can create reports and see how many tasks have I touched and dealt with in the past year or month. This helps the management team analyze the workload distribution and where are we spending most of our time which is sometimes not visible to all. Great feature during performance reviews.

Cons

I think JIRA can be very clunky and clumsy looking due to the format it is setup as. It could be designed to display the same information but I think in a much better simpler way. The huge icons and boxes sometimes gets too much for me. Also for someone who is new to JITA it is definitely not intuitive. There is a learning curve to JIRA. The process that I have to sometimes go through to create a request on JIRA for someone else is lot of work and there are some limitations on how the ticket can be created such as only one person can be assigned. The customization is JIRA is definitely not what anyone can do and always requires help from IT.

JIRA- Easy to Plan, Track & Release Project.

Overall, experience with JIRA is just awesome. Simple tool to maintain the team's effort and Project's status on a single page, Project boards. Would blindly recommend JIRA for simple and complex Agile projects. Happy Project Tracking :)

Pros

I have been working on an Agile Project and I would say this is the best tool for the below reasons,
* Better visualization of the project roadmap for the team.
*Customizable options, Kanban and Scrum boards that can be modified as per the project and fields to be displayed, columns on board for the flow of tickets, etc..
* Easy task allocation and tracking, from both Manger's and team members view.
* Allows the user to create/edit respective items, for example making file and screenshot attachments just a click away.
* Integration with other apps used by the project is simple. Namely apps like TestRail & Confluence.
* Best part is the backlog, which helps to create/track ticket then and there when required and work on it in future.
* Viewing logs is easy as every action is tracked.
* Easy filtering options and report generation for project statuses.
* Filter out tickets release-wise, helpful for regression.

Cons

For the simplicity of the application, I could hardly think of any major negative points.
I faced this situation so just sharing it. If the team member is released from a project he/she has no option to request via.JIRA to dissociate from the Project Board/unsubscribe from getting emails related to the ex-project. Inbox gets loaded with all the comments and action performed by the ex-team members.

Jira: An Essential Task Management Application

My experience with Jira has been fantastic. Overall, once a team gets used to the 'ticketing' structure, there are a lot of organizational efficiencies that can be gained. The standardization of ticketing can help teams navigate through areas of need and allocate resources from other projects if ahead of schedule. Jira works phenomenally as a tool to help manage projects both large and small. I have helped test and implement projects that have utilized Jira as the primary project management tool and believe that it is a state-of-the-art solution. Overall, I cannot recommend this service enough!

Pros

I use Jira for Project Management in my occupation. As a worker in a large enterprise, Jira does a phenomenal job of creating a fantastic user experience for both desktop and mobile. I think mobile project management is especially intuitive with this service. Where Jira stands apart from other standard project management tools is in its ability to track issues throughout an entire development lifecycle. Tickets are an essential component to keeping work organized and teams moving forward. The ability to collaborate via comments is unparalleled. Jira also offers extensive add-ons and pre-created templates for those just learning the service. When tracking projects, I never felt overly-encumbered by high learning curves or a clunky interface. Jira allowed me to work with many of the tools I am comfortable with and expand my potential.

Cons

From my experience, the largest pain-point / decision point between my team is on the issue of creating 'tickets'. While Jira is a very detail oriented application, this detail can sometimes become quite cumbersome. For example, the process of creating and resolving tickets can sometimes feel even longer than completing the task itself. Furthermore, it is difficult, if not impossible to close a ticket if you are not the creator. Therefore, project managers need to carry significant oversight as task statuses change. Therefore, tickets are very controversial but also an essential component to completing work successfully on this platform.

The "Ticket or No Ticket" Debate

It took time to get buy-in from the entire IT department to fully utilize JIRA. However, now that the whole department is all-in, JIRA has truly made our work effort much easier. We now have internal business partners who utilize JIRA to review work status, set priorities, and create new tickets when issues/upgrades present themselves. With an organization our size, I can't imagine not utilizing something like JIRA...not sure how we did it all in the past.

Pros

The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.

Cons

The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.

A project manager’s dream

A very strong tool for development projects, which covers so much more than just project management. Thanks to Jira, you can track issues over the whole development life cycle. Entire project layout is possible with infinite iterations, including planning and backlogs. The variety of collaboration tools involved (like comments) is unmatched by all other tools I’ve used. The project progress is easily tracked, plus you can track then across releases. Jira offers full reports on both progress and performance.

Pros

One of the best features I’ve found in Jira is the Workflow editor – I’ve never seen anything like it despite my extensive experience. Some people would say it’s not even that important, however, for growing businesses it’s something you can’t do without. Lots of task tracking is needed all at once, as you can never predict what necessities will arise in a growing company. Jira provides great help with all these issues. Sprints can be structured across multiple tandem-working teams, taking into account their wishes and preferences – either for traditional setups or for newer ones.

Cons

Honestly, one thing that was really off-putting for me was the impressively complex layout. The project list is simply huge, and you have to take some time to grasp the navigation and search features. Perhaps, in the next update the developer needs to add the possibility to tag or somehow categorize or classify projects more clearly to make them easily searchable. Otherwise, it takes a bit too much time. The dashboard is simple, but I don’t much like the visualization for reports. You also can’t assign tickets to several people at the same time. Only the person who created the ticket has the authorization to close it, which is quite bothersome. You can’t create columns or tables, and notes exist only for text input. I would also like to see a feature where you can generate turnaround time for ticket closure in an automatic way using reports. Plus if you have a bad Internet connection, there are issues with loading contents (sometimes the loading even stops altogether).

Expensive but extremely effective for project management

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)

Pros

- 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

Cons

- 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).

A very powerful task tracking system

JIRA is easy to use and great for managing work tasks on a project, however customization options are often only available to admins.

Pros

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.

Cons

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.

Flexible, powerful, simple to use and grows as you go

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

Pros

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.

Cons

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.

Managin Technical Projects The Right Way

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.

Pros

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.

Cons

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.

Collaboration Platform

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.

Pros

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.

Cons

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 usage for Agile 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.

Pros

- 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

Cons

- 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.

Business analyst - Awesome tool - Software administration

It's been a great experience using this tool for me

Pros

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.

Cons

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 project management software

Pros

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