Avis clients sur JIRA Software

Avantages

Répond tout à fait a nous problèmess de gestion et de suivi.

Inconvénients

L'implémentation est longue due a une ultra personnalisation possible. Le gestion des notifications est largement améliorable.

Avantages

1. It is very flexible and fitted really well with agile development work. whether you are using kanban or standard sprint planning work flow, it supports all of those.
2. It is extremely useful to do project planning and creating stories, they will be saved in backlogs and you can access them with weight, estimate and priority.
3. It is quick to create a bug ticket to track bugs.
4. It is very easy to plan for a new sprint, by adding task, stories from the backlogs, it helps with the total points you want to target for a particular sprint, it automatically sum up the story points and make sure you don't over plan.
5. great report tool to help you analyse the project completion and nice burn down chart as well. To help the team retrospectively go back and review.

Inconvénients

1. It is a big over complex by providing such flexible functionalities. But it is worth the time and learning curve.
2. As a developer, I don't have to pay the bill. But it is not very cheap if you have a large development team, the bills add up quickly.

Avantages

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

Inconvénients

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

Avantages

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!

Inconvénients

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.

Avantages

If you are willing to do the work, the advanced search is useful and the user experience isn't bad except that to eliminate done tickets you have to deselect all then re-select every option except those of a done type.

Inconvénients

Advanced search is the only useful way to reliably get information out, making getting even the smallest view of your data onerous. The core advantage of the tool - it's lack of structure - make it difficult to complete even the simplest of tasks without a ridiculous amount of effort. It's biggest failing is that everything is too flat by default. For example, I am working on a project now and the team has made duplicate tickets because the original tickets are too hard to find and are just dumped on the screen... we have sometimes used epics/stories/sub-tasks with sprints but these are truly inadequate... in today's time why should someone have to spend 20-30 hours a week grooming the backlog and writing searches when if the tool was any good it should (!!) be able generate these views automatically. We are now investigating other solutions like Wrike (absolutely no affiliation, not even sure we will switch to it) and in 10 minutes of testing we were getting views that we have been struggling to get out of JIRA for over a year. Also, you can't do something obvious like make a reminder in the future for a ticket, so you either get flooded with reminders for just about everything or you have to go outside the product to remind you to do something in JIRA. Seriously!?!

Avantages

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.

Inconvénients

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.

Avantages

Jira is an excellent project management tool. It is the best option for bug tracking and agile project management. Multiple teams can use Jira at the same time leading to a lot of integrations. Teams including product strategy, product design, and product development can collaborate together leading to improvement in project. Each team can track their individual milestones, deliverables, and tasks using the filter and search functionality. If you are using an Agile Scrum framework, your daily standup meetings are well supported by using custom views. You can create your own custom views to discuss only the relevant issues of the tasks. This feature is time saving and efficient for a daily ten minutes standup. The other new features that make Jira a must buy are due dates notification, assignment allocation, labels, assigning priority levels to tasks, and developing epic links which displays the user story and the project progress. For Kanban framework users, Jira provides Kanban boards where you can turn on and off features that you want to display or hide from other members. Jira provides high flexibility with features that maintain the tasks and deliverable backlogs and these features are applicable to different frameworks. Sprint planning, releasing sprint, and organizing history is very organized in Jira. It can be used for any type of project management. Customer support is available for Jira, which is very helpful.

Inconvénients

Jira has deficiencies on micro level. For a particular task, if you are maintaining the workflow, it is hard to customize the columns. Jira always displays all columns on a single view, more like a static view without scrolling. This leads to columns being smaller in width with smaller font size text, which sometimes become hard to read. Unavailability of scrolling leads to column being fit in a single screen browser. Pricing is also an issue. Jira is expensive and fits very well in the budget of big enterprises, but many for small sized firms it is a hard pass. Also, limited user excess to Jira makes it challenging to most small size companies. There is a trade off between ease of use and efficiencies. User has to have good knowledge of Jira navigation and customization before he can make the project management efficient. Customer support is helpful, but comes at an added price. Overall, customization, ease of use, and price are the biggest drawback for Jira right now.

Avantages

They've managed to provide easy to use projects, next-gen, that have most of the power but are SUPER easy to use. We love the new Kanban boards and the ability to turn off features and hide complexity wherever needed.

Inconvénients

The next-gen projects are moving fast, but it feels like at this point you have to choose *either* power *or* ease of use. Classic projects (power) or next-gen (easy) are competing, so I'm hoping they will be able to eventually provide all the power in the easy next-gen projects.

Avantages

Everyone knows Jira so it's simple to onboard new developers. Its simple to handle and prune our backlog.

Inconvénients

Complexity of some features and not refreshing views automatically. Working remotely on the same sprint planning with multiuser is a shit. Complex and chaotic.

Avantages

When planning sprints, work can be pulled in and estimated, the reward of being consistent with using this planning process is some great burndown charts for senior management to understand output and continual use improves estimation accuracy.

Inconvénients

It's fair to say that JIRA takes some getting used to and it's not the most intuitive software to use. It does seem the improvements to the platform, especially in relation to user interface are slow and for some time now, there has been a 'New' version that hasn't carried over older functions that were of value.

Avantages

This app is great for collaboration between a development house and it's clients. It allows you to clarify and consolidate requests from clients. User stories proved to be very useful in such aspects.

Inconvénients

Setting it up was a very complicated process, we were complaining about how hard it is to use until a new staff came and helped us with configuration of the workflows before it started to be useful for us.

Avantages

Flexibility in workflows and tracking separate projects and sub-projects in the same system.

Ease of creating multiple tickets as well as placing them into different projects without having to be in the projects portal.

Creating reports to review metrics is relatively easy, it was useful in an integrated project to review estimated times reported in previous sprints to project development times for other projects.

The flexibility of how tickets look and editable fields as well as workflows to tailor to the team and/or project being worked on.

Inconvénients

The bad part of Jira's flexibility is that settings are all over the place and you typically need to refer to Jira's knowledge base on how to configure custom settings whether it is for fields inside of tickets, workflow settings and automations, and many other settings.

The standard Jira end user interface is not exactly user friendly and some things may not make sense depending on the team using it such as a ticket being in a closed state however the resolution state has separate "states" such as do, don't do which is more used by software development teams.

Jira typically requires a lot of customization when setting up new projects either for project managers, agile software development teams, or integrated project teams. As an administrator this can be difficult to convey to my end users who want to track their projects in Jira. This is where you need to have great communication with your end users to be able to setup and tailor the Jira project to their needs and improve the overall Jira experience.

Avantages

1) Releases/Versions:
Releases allow us to work in parallel on multiple efforts with the same team.
2) Parallel Sprints:
Same as releases, we are a lean team and we have to work on Product features and polish/bug fixes simultaneously.
3) Custom Filters: I like these the most!

Inconvénients

They have taken out small pieces of functionality and made them separate products. These products are now paid and for those small pieces of functionality, you have to make extra purchases. e.g. Pages

Avantages

The fact that tasks can be organized and prioritized in every structure you can think of. I have used Jira in three companies and it was perfectly tailorable to all their processes. Also, it interacts beautifully with the other Atlassian-tools. Lock-In is no argument because you just don't go with Atlassian if you dislike the way their stuff works.

Inconvénients

Jira really has to stay ahead of its way less expensive competitors (FLOSS-guys, think Redmine). Also, it's weird how I saw some of our partners manage processes with Trello without having too much restrictions: that kind of made me think. You can probably go with a cheaper solution, but for us being a 250+ software-company, Jira was worth the price.

Avantages

Agile development on Jira is great. The ecosystem allows me to track my time, organize my issues into tasks and sub-tasks, track when things get done, create estimates, and organize complex projects into smaller and simpler pieces.

Inconvénients

The support is pretty ignorant of their user-base on several issues and refuse to add new features that would benefit hundreds, if not thousands. It can be very tricky to migrate, update, or set up. Plugins can cost money and it can add up, though I haven't spent too much at all for the value I received.

Avantages

I love the quick and easy setup of JIRA spaces and it's integration with other Atlassian products. There are also a lot of third-party integrations to help fill-in the gaps.

Inconvénients

JIRA is a beast. Plain and simple. Actually that's just it...it's not plain and simple. You have to have a good grasp of what you want from it to make sure you get what you really need. It is not friendly for the non-technical user looking to create a workspace.

Avantages

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.

Inconvénients

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.

Avantages

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

Inconvénients

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.

Avantages

I pretty much like everything about this software. It’s UI, features are great. The fields while
logging any issue/user story are extensive and self explanatory and there is tool tip too if you wanna know about the details of any field. For eg: you can format the description field like colours bold etc. this really helps while logging defects. This way it’s easy to understand the user stories too.
Secondly, attaching screenshots is quite easy. You can simply copy paste which saves time. There option of upload too but saving files and uploading is on effective utilisation of time I think. You can copy paste the screenshot directly.
Thirdly, issue search is good. History is maintained very well. You can search and filters tickets with any field and moreover there is advanced search where you can write a query (it’s very simple) to search issues. You can add delete columns and can also download an excel or cvs file. This results helped us in creating reports which were in turn send to the higher managements.
Another feature which I found very useful is agile birds and dashboards. It’s simple to move tickets on agile board and track progress.The sprints are maintained well.Dashboards has a lot of gadgets which you can customise and add. It’s give a very clear picture of the whole project and all team members. You can create multiple dashboards.It gives the latest summary of the project which saves a lot of time and effort when you need to share the report with the management.

Inconvénients

There at not much to write in cons section. But I think starting to work with Jira, using bas features, is quite simple but if you wanna use variety of features like advance ones, you need to explore them. Some features are not direct and you need to do the R&D. Like creating dashboards look simple but adding filters and complex gadgets takes time and will be quite difficult to implement in first go.

Avantages

JIRA gives me so much functionality out of the box. Within five minutes, I can create a board and invite my whole team to start working with me. It doesn't take long to customize your presentation of work to make it specific to your business. It has become the standard for the industry and with good reason; JIRA gives me everything that I need to track performance and ensure a timely release.

Inconvénients

There are occasionally some annoying bugs that will present themselves, but it's never something that really prevents me from using the product effectively; usually it's an annoying UI bug that looks messy or ugly. For the most part, many of the people that complain about the product just don't know how to use it 'as is out of the box'. The more configurations you try to make, the more problems you can create for yourself. Aside from this, their customer service is quite lackluster and it often takes days if not weeks to hear back from support - usually the bugs are fixed before you even get a response.

Avantages

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.

Inconvénients

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.

Avantages

Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.

Inconvénients

Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.

Avantages

Everything ! the software is very powerful, it has a lot of options and features:
- Scrum, Agility and flexibility of changing flows.
- Security setup for every type of users.
- A lot of features ( no way to compare it with any other software i know )
- Very simple to use
- Sprints support..
- High Availability.
- Awesome Designs ( old and new ).
And so many other things i love about JIRA

Inconvénients

I wish the cost was a little more less for small sized companies.

Avantages

We used several bug tracking tools in the past but Jira is by far the best one. What I like most:
- user friendly interface, provides a nice user experience
- Agile SCRUM/Kanban support out of the box
- extremely configurable on almost everything
- extendable through custom scripting, either built-in or via addons
- very collaborative
- there are thousands of addons in the marketplace; you can even write your own

Inconvénients

Being so flexible to be configured, the learning curve for admins is a little steep.
The price is based on the number of users and if you experience wide user adoption in a big company, you end up in paying more for upgrading to the next tier, than if you would pay for that tier first time.

Avantages

The backlog and features for managing the backlog with different methodologies such as Kanban, Scrum, or Kanban + Scrum hybrid are very flexible. Planning sprints, releasing sprints, and looking at history of what was done is very organized.

Inconvénients

Cumbersome to setup. Workflows for issues and UI/UX for creating them is not easy to understand. Sure you can figure it out, but it will require a lot of facepalms. It's good for larger organizations with several cross-functional teams, but if you are a smaller organization stick with Trello and checklists for the cards if sub-tasks are needed. The sub-tasks in Jira are just plain awful to work with, and will end up wasting a lot of time for your team.