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.

A great number of functionalities. On the basic level is intuitive. Vast possibilities for adaptation and customization. Rather easy to integrate with other apps. A huge number of plugins. Customer service - in terms of personal help to do something

Some features are limited (e.g. filtering) Customer service - in terms of requests to add new/change existing functionalities. Rather high price

Web based product that was easy to deploy

Building automation was very cumbersome and did not always work. For example I spent way more time that expected to build a simple automation trigger that when a scope item is closd, all the children tasks under it should close.

Based on the feedback from developers and teams, the most appreciated feature of Open DevOps is its comprehensive nature, which offers a wide range of tools and functionalities for modern software development and deployment. Developers can leverage the platform for version control, continuous integration and deployment, task management, project planning, task progress tracking, status tracking, and more, all in one place. This integration of tools and functionalities in a single platform enhances productivity and collaboration among team members, making it easier to manage complex projects efficiently.

This can be a challenge for new users who are not familiar with the tools and technologies used in modern software development and deployment. Additionally, some users may find the pricing of Open DevOps to be relatively high, especially for smaller teams or startups with limited resources.

Sprint planning is easy and very helpful. Productivity is enhanced many folds after using this. Team work becomes stronger Easy to convey things between a team Easy to track team member's work Team performance becomes efficient Integration with tools makes the tasks efficient to process Product road map made easier than ever Used by software developers of Expedia

Certain limitations are:- In the beginning it is difficult to get used to it. Collaboration feature is missing It is basically made for software developers. A little expensive In the beginning managing tasks can be a challenge

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.

I like the ability to control workflow, tasks and resources. It's a great way to keep a team organized and on schedule. Integrates nicely with other development tools and has an easy to use interface. Most users coming from other similar tools can hop right in.

We are currently still using Dev Ops for our repositories. This tool needs the ability to push and store changes and versions of files.

self explaining, a lot of ways to customize to meet your requirements in the project. Not only useful for project managers, but also for developers/analysts.

I have seen several instances and the tool seems to work a bit slow overall. Also when multiple users work on the same item simultaniously there are issues sometimes. Dark theme is totally missing.

We used Jira every day for development and Product management for creating, assigning and updating tickets ,user stories and tasks.

Though it's A very useful and easy to use and riched with features but scrum methodology I think Azure devops board is far better in sprint management

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.

Perfect for resource management and issue tracking, good for project managers to find out where the team is spending maximum time and helps in bandwidth allocation, understanding team velocity. With the Atlassian Suite, Jira + Confluence is a deadly duo.

Very slow! The dashboards are not fast. Also, for milestone tracking, percentage completion is not very well implemented as well as time spent does not get that much of visibility.

Easy to use and follow. It doesn't bog down with too much process. And the process can be built as you want it.

Took a while to get use to where the + button was for adding a case.

Jira is a very powerful tool for managing teams of software developers working on one, or even multiple projects simultaneously. It is very robust and feature-rich, with features such as setting up/managing individual tasks, coordinating development efforts across tasks/developers to maximize team productivity, managing/tracking issues & bugs, gathering feedback from non-technical users via Jira user...

Read more

Given the robust features and functions that Jira supports, there's a lot of depth and breadth to the software, so it can be somewhat complex and confusing to newer users, especially those who haven't worked much with project management tools previously. For project managers who are leading multiple teams simultaneously, things can get a bit overwhelming because the email notifications and project alerts can quickly start to become excessive, and there's no way to consolidate notifications across projects/teams.

Supports integration to most of the developer's tools Complete freedom to design your own workflow and screens An automated ticketing system can also be generated with its Command line interface and workflow Customer Support is one of the best in the corporate industry Multiple tools have given at user end to make admin changes easily like, Restarting tomcat, re-indexing or integration with SVN, git.

Expensive for businesses who are medium size Upgradation of the software from one version to another requires real IT skills If you want to keep Jira running smoothly it has the indexing feature to make it faster but sometimes those index gets corrupted and no one can help in restoring those data.

Completely business integration, the only one system which we use to every processes in the company

archive of project without indexing in the basic server version not only in the datacenter, it is very, very expensive

- Everything-and-the-kitchen-sink approach that caters almost all enterprise users. - Fully extensible through plugins - Allows deeply integrations within different teams - Without doubt, helps boost productivity

- Some of the best features are hard to find - This is the worst one: there's no way to leverage the fully potential of the Search functionality without learning it's own querying language -- which is totally nuts because this should be dead simple to use - The iOS companion could have some love by extending the application functionality. In it's current state, besides some light editing, it is mostly a view-only app, which makes it unusable when you're away from your computer

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

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.

1. Works like bug tracking tool 2. Efficient project management tool 3. Easily assign the issue to anyone 4. Easy to search any existing story 5. Drag each of the stories into a single spring. You can prepare sprints in minutes if you have already created stories. All you need to do is assign a timeline to the sprint.

1. It is a complicated and heavy tool. Thus, it needs dedicated tech personnel to manage the same. 2. There are cheaper alternatives in the market.

Tracking issues that allow us to tracking bugs between developer and tester.

It is generally a good app, but it lacks the most basic feature, requiring me to use a laptop instead. The app would function for me if there were a copy issue URL button like the one next to the ticket number on the web version. Due to my habit of sending and referencing tickets across Slack, the lack of the ability to copy the URL to the clipboard makes this app nearly useless for about 90% of my needs.

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.

In my role as a Project Manager for software development, the developers used JIRA to manage the development cycle and we jointly use JIRA for problem reporting, testing, quality control and resolution. JIRA provided and tracked the information between groups so there was no confusion as to the status of a particular issue or trouble ticket. The ability to review "tickets" and see the status was very beneficial from a management perspective.

There was somewhat of a learning curve just to get started but that improved with repetition. Although I was not directly involved with setup and configuration, that seems to be a little more complex than originally though.

I love JIRAs ability to interact with both HipChat and Confluence. I also love the ability to run 2 week sprints with my team and easily see the progress of each of their tasks.

"JIRA Spam" - I am an admin user at my current job and enter a lot of the tasks myself. Due to that I am a 'watcher' on most all of our tickets. I would prefer to receive less email communication regarding the status updates of each task. There are so many emails that they tend to be ignored due to over communication.

Visual, real-time, fast. Great for logging, tracking and monitoring bugs and enhancements. Great search functionality. Made project management much easier with greater visibility of workload and any issues that are stuck or blocking progress.

My organization tried to use JIRA for bottom-up project planning by defining features, applying estimates, linking etc. This level of deconstruction didn't always fit well with how developers work and ignored the big picture in some cases. The result was massively overestimated timelines and overwhelm for the team.

It has a good API, good integrations, is highly customizable, and is pretty good at tracking features, bugs, and backend tasks.

Navigation is cumbersome and its often difficult to access various functionality. Their search is powerful, but geeky and difficult to use; a simple universal "search everything" box as the default would be better than their syntax-heavy search approach. However, the most frustrating aspect for me is the total lack of label management (labels are Jira's version of tags, but they are not editable as relational objects). Some development teams also try to use it as a project management tool and it just isn't great for that.