Best and most true to tradition agile project/product management tool around
I have a (probably unhealthy) love for Jira and would need a lot of convincing to switch. It's interface is genuinely enjoyable to use and it aligns perfectly with agile product management methodologies, natively and in conjunction with its plethora of add-ons.
Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.
The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!
Enterprise Task Management
Jira is a strong, industry-standard project management and task tracking service that is flexible enough to allow different types of teams (software, legal, IT, etc.) to work on the same platform.
Jira has a strong SaaS-based offering that makes the administration and operation of the product simple and easy. The software has multiple options for viewing tasks (from project-task style to Kanban style) which allows different teams to be flexible and use different formats.
The difficulty of running the hosted version of the software with custom plugins is almost unacceptable for enterprise-grade software. The concept that enterprise project-management software requires dedicated IT assets to service and maintenance increases the overhead of the software to unacceptable levels. If a deployment requires a host, non-SaaS version of the software with custom plugins, reconsider.
Works great for Software Project Management, I wish the configurations were easier to set up.
We are overall very satisfied with the product as the user side of the things are very solid. The administration is quite complex and if you are doing it on your own, it will take a long time and a lot of hours reading their forums to get things right.
The task tracking and overall reporting are pretty solid. If configured properly, you will not miss on any updates and can proactively resolve blockers.
The configuration. They are very complicated and you cannot expect a new user to get it right and that's why there are dedicate people who set up this. We did it on our own and it took us a couple of months to get things right.
The software an engineering department can not live without
Jira cuppled with Agile processes have driven the velocity and overall engineering teams to new heights at the company. I don't see a world where once you are on it you are with it for better or worse.
First of all I want to say Jira is DOMINATING the market. There is little that Jira cannot do which makes it a no brainer of everything most startups and companies will use. I love that Jira for the most part is a one-stop-shop for Engineering teams, IT teams, Knowledgebase, ticketing systems. You don't really see issues with using Jira until you get bigger. The fact that I can link Jira tickets to my Git commits and add confluence documents to my tickets and google drive files ALL IN ONE is ourtagious and its something my company loves inside and out.
Just like every software out there you cannot be perfect in all ways. Because Jira is a one-stop-shop the biggest issues we have is customization of Jira. Not because Jira cant be customized, but only because it can be customized so much that we need set Jira admins whos sole job it is to manage Jira for the entire company because of the huge learning curve because it takes so much time how to figure out even the littest changes to make our lives easier. On top of that, a big issues I see if that as you grow in Jira it is a money pit at times to have it scale with the company. At this point, we are so vested in Jira we cannot get off of it. Adding SSO, and Confluence, and CI DI, and all the features that they promote arent dominating their fields, but its like "Well.... We are on Jira and they don't integrate well with other software so if we want the best features I guess we will have to use all their software"
Great for time tracking and task management, but some functionality is overly complicated.
As a project coordinator, I use Jira daily in a project management aspect, matching our planned work to progress completed by our teams. I maintain an overhead view of in-flight tasks and projects, and compare this data to outside sources we use for resource management, capacity to contract, etc. My most frequently used elements are a custom KanBan board which shows all in-flight, assigned issues for the entire company; as well as Tempo time tracking software and the reports tool.
I love the KabBan task view, our company uses this every morning for a company-wide standup meeting. We have set up a customized board with cards that display budget/due date/time spent/etc. and it has been invaluable to us during COVID-19, as we are all working from home and need to stay connected.
Jira's time logging via Tempo has some buggy elements, but has been absolutely crucial in maintaining a clear view of task progress and budget maintenance. The time logging tools are incredibly reliable and allow the perfect amount of editing control by both administrators and users.
It is a big pain not being able to assign more than one user to an issue at a time, especially when making Jira issues for meetings, as the purpose here is to provide an issue to log time against. It has also been difficult for our company to systematize and homogenize project structure, as there was such a large learning curve to Jira project setup, and we have a large number of open projects. The functionality between projects differs greatly, and I think a large part of this is due to complicated project setup and maintenance. While Jira is very developer-minded, and many of our developers like it, it seems a slightly less appropriate fit for our designers/strategists and project management team. I also lack the ability to export some reports I need, for example a clear Estimates versus Actuals report in CSV form.
The industry standard for managing the Software Development Lifecycle
I've used everything from Excel spreadsheets to MS Access to MS Project and I find that JIRA is the best bang for the buck when managing our SDLC.
We use JIRA online and it's dead simple to create and manage complex tasks. I love the ability to integrate with great packages like Confluence (which is SOOOO much better than Slack!).
Getting new employees up to speed on using the software is more time consuming that it should be. I'd prefer a more intuitive UI.
The most Advanced Managment Software
Overall this is the great software for Product-process management and for issue tracking.
Firstly Jira is the most advanced task management software in my opinion. It has tons of valuable features for issue tracking, has interfaces like scrum, kanban and etc. It has simple mode for an starting projects and very advanced for more complex projects. One of the great things it is the editable everything e.x statuses which helps to my my team to do process more likly.
Using the Jira API it has little drawbacks for example complex documentation. It does not have major language libraries and sometimes the the API is not stabile.
Using Jira Software and Service Desk
We have been using Jira (and Confluence) for over 10 years. We currently have over 500 projects in Jira with a user base around 2000. We do agile web and app software development and run a support desk with kanban. Each team has their own projects with their own specific needs, from workflows, custom fields, permissions, and notifications. We do not use the cloud product, but a 3rd party, hosted, server version.
Extensibility. Jira really can be all things to all users. There are so many business workflow processes that we have implemented and all in Jira: advanced software development, workflows for processing contracts and invoices, and support work with incidents and service requests with approvals.
Lastly, with the large dev community and a large pool of app add-ons, we are confident we could extend Jira to be what we need it to be.
If you don't understand the principles of Agile software development, there will be parts of using Jira that will be foreign to you and will likely go unused.
There is a steep learning curve on the administration-side. With so many functions and features, it can be difficult to know all of your options. The "schemes" that power the project administration can also make it difficult to troubleshoot your setup.
Effective Agile business project board
We used JIRA for agile development and testing projects for tracking status. Multiple scrum and agile masters used JIRA, resulted effective outcomes, tracking in a easy way and watch out without a delivery miss. Creating sub tasks within task lead to deep level of monitoring work items, given confident to manage the task items. We have used user stories, back logs, mini sprints, daily hour stand up calls which given target throughput accurately. Used JIRA in the form of test cases, defects, change request types, requirement analysis - all forms of software test and development life cycle along with multiple development tools like dotnet, GitHub, etc.,
Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.
Sometimes I feel, the JIRA GUI is clumsy to have many things in dashboard, other than that I do not see any specific negative factors to hate JIRA, and it depends on how we use the features for projects.
Jira for test management
As a QA in the team, our project is fully customised for tests, and Jira with Xray so far provides the best test management tool in the market. It makes life way easier, it is better than Zephyr and of course much better than excel sheets, which saves time, energy and money for us as testers and for the project.
The organisation of tests and the variety of the issue types for testing (Features ,Test cases, Test sets, Test executions, Test plan, bug...)
The ability to track the executions of tests and bugs
Great adaptability with Gherkin and Cucumber
It goes perfectly with ISTQB standards for testing
Perfect for both Scrum and Kanban users
The great boards and views provided by Jira (followup dashboards, sprint board, ..)
The ability to add Xray or Zephir or whatever test plugin that suits you
Jira users must receive a training before starting to use the software since it can be a little complex to use the software for the first time
For testers you cannot execute the same test case more than once in the same test execution
It gets more and more difficult when end to end testing multiple applications at the same time
Go Agile with JIRA!
Jira is very easy to use from the user perspective, as well as operating it from the Admin perspective. Overall I personally suggest this product, although its price not being very welcoming, it's definitely worth the money! If you're a very large organization you definitely will want to try Jira.
Jira is a very good platform for organizing your team and projects using Agile/Scrum or Agile/Kanban. Whichever option you will choose you are covered! With its extensible platform through plugins you will never get tired of Jira. The installation is pretty much straightforward and with latest versions you can also make it HA, for instance on AWS, quite easily.
Although the product is very mature, feels also like a big giant monolith although its plugin architecture. Also, plugins are too much expensive for just simple features. There should be much control from the Atlassian Marketplace, which should follow more an App Store logic like Apple's or Google's one.
good tool for project management
Collaboration of our team has improved after we started using Jira, the tools helps in planning and identifying gaps while we develop features. The mobile application is really good and one can get work done from mobile app as well. Overall Jira suites our needs.
Jira is very flexible and can be used for different use cases, eg: project management, issue tracker, road maps etc.
It is quite easy to configure compared to other generic project management tools.
The transition from old user interface to new one, it is very confusing, the UI is not consistent when we visit URLs from email notifications.
Compared to other generic tools, Jira is quite easy but still it is not easy to setup, it takes quite a few days to configure the system as per needs. It would be great if there were boilerplate templates.
Jira...the best out there
The overall exprience has been HIGHLY positive. Jira is the go to software for project planning and coupled with Jira Service Desk and Confluence (which we use at the moment), it is a very truly powerful piece of software. I have tried other ones, but always came back to Jira due to it's widespread acceptance and ease of use.
Jira is highly customisable, and also has plugins. It allows you to monitor your projects and provided granulated access to individuals. You (or your admin) can set roles for the project and associates those roles to certain activities and then associate the roles even further to individuals.
You can organize your tickets in sprints and releases as well as monitor workload and task assignment to your team during sprints (or whatever other form of software delivery you wish to choose).
Pricing model. Currently, you have a choice of server vs cloud setup. If you have a team that can maintain the server instance, I'd recommend going to server because you have a lot more plugins you can use on server and you can set it up the way you want. The best thing is the licenses are a one-time cost, as opposed to lower, but monthly and forever costs on the cloud portion.
The other thing that is to be considered is that the plugins you choose need to have the same level of range for hte user count. i.e if your jira is for 101-250 users, all your plugins will need a license level of the same range, i.e 101-250 users. Something to consider if you are thinking about moving to Jira.
Flexible but not at all fun
Originally we wanted Jira to be the place for Product and Development. But we soon realised that we needed a separate app for the product team instead. So now the product team work outside Jira and only when it's ready for Development will a ticket get created and planned in the backlog ready for a sprint.
Jira helps the Product Manager to know the status of features, bugs and tasks and allows the development team to ask questions relating to the ticket in the comment section. That way there is full visibility of the discussions for future reference.
The biggest strength that Jira has to offer is how customisable the app is. We're forever fine tuning how how development flows are setup and I've never run into an issue where what we wanted to achieve could not be possible. The workflow editor is pretty straight forward once you figure out how to map these to specific projects and features.
It also has a mammoth number of apps that can integrate with it, which can greatly help simplify your organisations stack. We use a bunch of apps that connect to Jira such as Slack and Git.
The mobile app is pretty good and more simple to use. There's also a new iOS app that you can run on a mac that seems to be a slightly faster and more user friendly version. However, I haven't quite worked out how to tailor the notifications.
The search is very powerful!
It is very slow to load pages and jump between stories. When using this on a daily basis it really gets annoying.
When we need to change a setting it's hard to work out where to go. I have to say I've never seen another app quite like Jira which has so many different places to go to in order to change very similar settings.
If someone accidentally creates a ticket with the wrong type the only way to change it is to Move the ticket. And I can't seem to change the status of the ticket at the same time. So often an Open bug ticket becomes an Open feature ticket, which really should still be in Draft.
Powerful, enterprise software that might be more than you need
We use Jira as a kanban/agile project management tool in software development. The workflow is well understood by most developers and onboarding new team members into our system is a breeze. It is good at tracking projects and managing sprints.
As an SDLC management tool it excels. It's designed from the ground up for tracking user stories, tasks, epics, sprints, etc. in large organizations. It is excellent for cross functional team collaboration and really shines in a mature environment that doesn't change frequently or quickly. It is continuously improving and it is obvious that the JIRA team is very proactive and dedicated to staying ahead of the competition in features and services.
It is overkill for smaller teams or products that are very early in their life. When projects and teams are very dynamic, Jira projects become bloated, cumbersome, and fragmented. This product really is suited for larger, mature organizations that already have strong procedural discipline and rather monolithic approval/decision making. I know it's supporting agile methodology but really it's rigidness is more aligned with waterfall type management.
Perfect Combination of Customizable, Detail-Oriented, and Easy to Use
I love JIRA. I use it professionally and personally. Even though it is primarily a task manager for software development, I have found that it is flexible enough to be used for all sorts of projects. It is amazing how customizable it is; you can configure your project settings to your already existing workflow, whatever it may be. While the initial setup can be time consuming, once you have your settings configured, using the tool is a breeze. It takes seconds to create tasks, start springs, evaluate progress, etc. I find that this makes JIRA standout from other task managers. In most cases, if the software allows for detail-oriented task management the process of inputting and tracking the tasks themselves is cumbersome. Entering and tracking tasks should not have to be another time-consuming task! The JIRA web application is also excellent, making it easy to enter or track tasks on-the-go.
I think there is a lot of potential with Jira's NextGen projects, however, the software rollout has been uneven and often not well documented. I wish this process would have been better thought out to make transitioning to NextGen projects smoother.
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 :)
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.
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.
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.
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.
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.
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.
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)
- 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).
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 is a project management software
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.
The defacto standard for Ticket Tracking and project management
For usage in a relatively larger tech environment, JIRA has a been an indispensable part of my workflow. I use it every day to not only track my work but to communicate my progress to others (and vice versa) and to plan and resource our sprints.
JIRA supports many features out of the box and offers plugins to expand its features.
However, if I were in a smaller tech organization, the huge variety of features and customizability might be a bit overwhelming and I would look for simpler tools to get the job done.
In larger engineering/product organizations, it is the de-facto standard for issue management and I highly recommend it.
- Very easy Kanban board and ticket tracking
- Linking tickets is very intuitive and useful
- team collaboration through pointing, filtering
- Full of features
- Expandable with plugins
- wish epic management could be done better. E.g., wish you could have epics of epics
- wish it was more intuitive to search past tickets, however reporting is available.
- Sometimes performance seems slow
- For people who don't need very complex task tracking, JIRA is a bit too bloated with features.
Great tool to improve your workflow and project organization
JIRA has honestly made my project management life easier. I can keep track of everything and since everything is so well organized, I can either look into the future weeks and see or organize how my work load will be and in case I don't recall how an issue was solved or who fixed such issue, I can easily travel back and look at the old tickets and archived content.
I like JIRA thanks to the versatility it offers. The type of boards and features whether it's for AGILE or SCRUM project development or for it's tickets organization and how easily I can assign tasks to myself or other coworkers. Also I like their support desk system since with the portal I created, My customers can report issues through the system, I'll get a notification and get on it as soon as I can, or it'll be created as a ticket/issue and I'll get to it when I'm available. Also I can assign this task to someone else for them to take care of, or if it is related to another department.
I would say they have improved with the time, but one of the minor things I disliked about JIRA is how slow it felt sometimes. Like if you have a project or board with a lot of issue/tickets, it's takes a lot of times to load, or performing actions on it can feel sluggish, not work or just bug itself. Another thing, that they have greatly improved with the recent re-designs, it's how hidden some features were under a menu (...) menu, when before there was a dedicated button for such important features (moving issues, closing etc). Now, they've changed it but I don't know why they made the change to begin with.
All you need for your day to day projects and tracking initiatives
In general, this is a highly recommended tool it fits well with any type of organization and it could be customized accordingly which is great. I love that you can make recommendations and they listen to you and implement the changes which are great.
This is our main tool for tracking and monitoring out day to day activities in the project management world. it is pretty solid and intuitive and it has helped the team productivity greatly. It is simple to use and out of the box it simply works just fine
I would like to have more control over automation options and APIs that I can use to control it. in general, it is good enough however if you are in CI/CD environment it will need more love that you would like to automate it