Open DevOps Reviews

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.

It is a brilliant tool for both tech savvy or even otherwise and We have been using in our company over few years and we have customized to suit our needs very easily and good customer support

Integrating with external tools could be tricky and not much support available online and could be done better

Its very simple and efficient tool to track, manage projects and capture efforts .
It gives very clear idea of status of project (in-progress, ready to test, ready for release etc) , items being worked on in the project and team working on it under one tab.
A tester can raise defects with severity under project tab and assigns to developer which automatically informs developer through email. Developer fixes defects and assigns it back to tester.
It arranges the work assigned to user on the basis of priority shows it on the very first dashboard page after login.
It has capability to log hours along with description of work done. The hours logged can exported to report format and verified for every member working in project.

Not big cons as such.
The only con I see is it does not support peer programming. Any issue can be assigned only to one person. If multiple people are working on a single issue or multiple leads are reviewing code jira does not really have capability to support this.

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 has a clean, updated interface with powerful issue tracking features for managers, team leads, and developers. Features I like the most are the advanced issue search, integration with Confluence, easy navigation, quickly create new tickets and build sub-tasks, epics, etc. out of them. Our management and team leads like all the labels, components, and other content management features of the tools. If used correctly by developers, JIRA makes it easy to trace-down issues, and understand decisions made in the code. You can notify other users of issues with easy "@username" in the comments.

Formatting text can be a little tricky. Kanban boards don't come for free for all users. Sometimes it's slow in updating tickets (granted that could be our server it's hosted on...).

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.

Gives a real granular approach and accountability to your work. It allows for everything you do to be tasked up, with time frames associated. Helps with project planning, and giving time estimates for deadlines. It also allows us to early on see if a project is going to slip, if any early tasks slip.
It has given our company a much better agile approach to development.

The software isnt intuitive, and relatively feature rich, making it complex to understand how to use it to its full potential.
We have some issues, which seem to create a lot of admin work, such as once a task is done, there is no easy way to put that task into review. The best way, is close the ticket, make a new ticket that is review and assign it to someone, which will need to go into the next week sprint to not affect sprint stats.
Also no ability to assign multiple people to a ticket, such as a review for 3 people to look at. You need either 3 seperate tickets, or 1 master ticket and 3 sub tickets (not ideal if one person doesn't complete it within the sprint, as it pushes everyone into +1 week late).

I see JIRA as a strong match for agile programming.
I like the ability of the sprint management, easy filtering of the Canvas board by multiple filters (like name/component/etc.).
I also like that it can be integrated with GitHub:
- I can see all the commits and pull request associated with the story (and it saved there forever)
- The stories automatically flow in the sprint canvas boards when the status of the pull request associated with the story changes.

A lot of bureaucracy is required for opening a new JIRA story/bug/feature/etc. I understand that this inevitable, yet, it's very confusing at the beginning and requires some learning curve to get into the software.

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

You have the ability to implement many extra plugins that have been designed specifically for JIRA. There are a lot of customizations you can make within the interface without the need for addtional plugins as well.

There is a lot of manual setup required. A lot of times, it seems like you need to create multiple pieces within the console in order to get something working properly. When I would set up new boards and categories, I found myself having to redo my work on a few occasions because I would miss a setup when setting up certain references.