Avis clients sur Open DevOps

Easy team task tracking, efficient sprint planning, and organized confluence. All and more is very easy to use and adapt.
Epics and stories help you to divide the project into parts and assign divided tasks within the team. In this way, you can follow all of the elements of a project in detail. And no step escapes from your attention. You can also distribute the workload very planned and provide team collaboration.

Sometimes connection is low. But overall, it's really beneficial.

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.

The customization and features it has are awesome. We can do lots of project management things with Jira. Definately one should try for their projects. This is the best among all project management tools

I really don't like much their UI. It can be improved. Especially in latest version of their UX, the navigation sucks.

Ease of use for both business (access mostly front-end reports, dashboards & Confluence) and developers (access mostly JIRA boards)

I'm currently trying to work with our developers to integrate Azure DevOps (where the code is housed) to JIRA in order to track code and link code with JIRA stories that are worked on. The apps to do this in the JIRA app store aren't great and we're encountering more issues than we expected. It seems as though JIRA integrates with a (soon-to-be) outdated version (might be using the wrong words) of Azure DevOps that my team no longer uses.

Having worked with several QA and development teams, Jira is a fantastic tool which can be tailored to fit just about any software development project. I enjoy that the standard feature set is powerful and easy to setup, but it can also be expanded upon using custom programming or third-party extensions. Given the product's prominence in the marketplace, it's easy to get started with a new project and quickly get the entire team on the same page in capturing bugs, tasks and feedback and moving work through a process.

As flexible as the system is, there are times where Jira simply isn't able to accomplish a task in the most straightforward way. As a project planner, the number of organizational levels (Epics, Stories, Tasks and Bugs) can seem like an appropriate amount, but each of these levels need to be customized in order for the system to meet the fundamental requirements jira has in place out-of-the-box. What I least about Jira is that is seems to have an "attitude" about how work/tasks should be organized. As soon as you encounter something that is not in line with that attitude, you end up needing to tweak a lot of little things in order to get the result you want.

Full control over every angle of the process. The UI/UX of Jira is getting better and better over time

Requires a lot of time setting up the process and maintaining it. Training is almost a must if you want anyone to understand how to use it correctly. The performance of Jira in web browsers can be quite poor from time to time.

1. Supports Issue tracking, task management, project management and collaboration.
2. Easy to create user stories, divide into sub tasks, track the progress of the tasks, label, categorize and prioritise tasks and we can get a complete picture of project goals.
3. Supports different reporting such as burn down/up charts, velocity charts, estimation, etc.
4. Out of the box many integrations, including atlassian confluence and bitbucket integration.
5. Highly customisable dashboards and supports sprints and kanban boards.
6. Task notifications and linking of tasks to other dependent tasks.

1. Sometimes it takes very long time to refresh/load the board.
2. Quite a learning curve since lot of features and sometimes becomes complex for new users. So initially its kind of time consuming to put efforts in learning the tool.
3. Sometimes get unknown token error and then we have to reload a page.

One of the things I liked most about Open DevOps was its extensive collection of open-source tools and resources. The platform provided a wide range of DevOps-related solutions, including continuous integration, deployment automation, configuration management, and monitoring. The availability of these tools in one centralized platform made it convenient for developers and operations teams to collaborate and streamline their workflows. Additionally, the active community support and frequent updates ensured access to the latest features and improvements.

While Open DevOps had many positive aspects, one thing I liked least was the learning curve associated with some of the tools and technologies it offered. As an open-source platform, there were instances where the documentation or support resources for certain tools were limited or less comprehensive. This required additional effort and research to fully understand and implement those tools effectively. It would be beneficial to have more detailed documentation and user-friendly guides to support users, especially those who are new to specific technologies.

Jira is a great product for not only CICD but also tracking of project

Looks complex to use sometimes. Menus are not always user friendly

It has a customizable architecture that supports a variety of procedures for development and deployment. The software development lifecycle is automated at various phases, enhancing teamwork between the development and operations teams. It provides a useful and effective technique for developing, delivering, and overseeing cloud-based applications.

When there are many users using this portal, it could be very slow. For some more complicated tasks, it can be challenging to use. It can be necessary for team members to take pricey training courses and learn new abilities.

Jira is a one stop shop for tracking all issues we're working on, from bugs and tasks, to users stories and epics. The tool can be customised lots so can easily be set up to suit your team's needs - different fields, workflows etc. It's been a crucial part of ensuring that all requirements are captured, not lost and that our development, testing and release activity is smoothly managed.

Confluence is a great part of Jira too and has replaced clunky document management on cloud based storage solutions or, even worse, someone's desktop..

I feel that Jira is not the most user friendly. It took a long time to become really comfortable with it. There are a fair few inconsistencies throughout the system too - e.g. releases can be called releases, versions, fix versions... little things like this just make it a bit harder to adopt.

While Jira is a reasonably complete solution, my team still finds themselves reverting to spreadsheets and capturing info outside of Jira from time to time.

It is pretty decent for running a team. If you don't really care about devops much, it is a perfectly good tracker.

I hated getting nickled and dimed with integrations for documentation (confluence) and source repository (bit bucket). It is also missing a lot of usability features that they just haven't kept up with in the lines of sorting and searching.

We're a marketing team but use scrum development rules applied to marketing and JIRA has been an amazing, customizable tool for that. Automating workflows has been really powerful. Tracking points has made us far more efficient than we otherwise would be. It's greatest strength translates into it's greatest weakness. When you pack so much power and methodology into one tool it becomes a much more niche product built for specific people and can seem difficult to use. But, that's what we love about it. One you learn it, it changes the game.

In order to use JIRA you need someone or multiple people that really understand agile development and scrum to make it work. Otherwise, you won't be able to leverage it's power.

i really was amazed when i began working with jira,it has alot and i mean alot of features.
As a developer the most important for me was Ajile boards and how it's effective in sprint planning and working with scrum.
also bug reporting and fixing became easy,and also you can make integrations with many apps and tools like slack ,github and many more.
how over due to so much features you might get lost in the beginning,
if you don't know where to start.
but never the less ,i highly recommend it for any one in the tech field specially developers and busines people.

the UX is not very appealing and could use more work.
maype more seperation between features