Open DevOps Reviews - Page 4

Jira handles almost everything in an agile environment, including backlog, to maintain version in bugs. This tool is very helpful when working in an agile project, where stories and bugs can be assigned to multiple people, comment with tagging users, giving reactions in comments are all useful features. In every ticket, saving the history of the ticket is very important where auditing can be carried out as to what happened to the specified ticket.

Editing confluence pages has become very slow, where sometimes the page needs to be refreshed in order to get it functioning. The User Interface in working and adding components to wiki documents is not straight forward. Sometimes, we need to search on how to add certain segments on wiki to know how to use confluence on Jira.

I like that this integrates well with github for pull requests and provides so many convenient ways to visually display tasks and projects and keep track of it all. The search function is very helpful as well.

Editing workflows is very difficult when you need to add a new status. The help articles describe a very intuitive method for doing this, but the link they describe is not found as easily as the article says, and I struggle with fine-tuning the workflows that were set up by a predecessor.

All project management activity in one tool. All as it is used in most of the organigation. It saves time in onbording. Can Manage Sprints boards.

Must be more user frendly. Some time I feel creating a new task is a time conduming process.

Ease provisioning of JIRA/Confluence/Bitbucket instances. Free tiers helpful., Support is very good too,

Plugin ecosystem for cloud is much smaller that JIRA DC

I love Atlassian products. They in recreate so well together. For a task management system Jira is definitely more versatile than others I've used.

Setting up some of the forwarding systems is a pain. But the abilities that jira has is definitely worth the hassle.

JIRA is great for managing a high volume of issues and tickets. As a project manager, I appreciate the ability to create numerous filters and dashboards to keep track of issues at a high level. I also appreciated that whenever a new idea or workflow need arose, it was more than likely possible with the right configuration or add-on.

There are times when I wish the platform were simpler and had fewer configuration options. At times I was paralyzed by how to proceed with a workflow update because the control is so granular. That may be a less attractive aspect for me, but I'm sure others love the granular control.

A great platform for software development using agile methodogies . Without Jira it is very difficult to manage the status of product development . Provides a common platform for defects raising , task tracking with detailed report burned down charts . Its rest api is for any developer is a great feature . Thanks Jira for helping the developers , It really makes our task much easier and efficient and smooth .

Apart from its loading speed , I could not find any cons . Best tool for agile . Loved it .

The software bring on so many functionalities and capabilities to track not only the progress of different teams but also the possibility to add custom filters that later on can be used to see the progress, impact and velocity of teams. The customisation is great. And recently the new UI has made the UX perfect

Some options are kind of hidden and sometimes you can mess up not really knowing where to hit for specific data. It is easy to access a board and see tasks progress but later on to see historical charts, things can be more comlex

Capability to store Epic, User Story, Task, Sub Task, Test Cases, Defects

Navigation and UI is little confusing, Administration is little confused

I liked Jira for its history. I was able to go back to the beginning of use to gather information on previous projects.

I didn't like the user interface. Some of the tools were not intuitive. I later learned that the tool was designed with coders in mind. I'm a marketer, so I think that was part of the reason.

The software allows to have both a great overview and in-depth details about software projects. The large variety of configuration options allowed my team to tailor the issue workflows, issue filters and agile boards perfectly to suit our needs. The UI is nicely polished and, most times, very intuitive.

It has a really high learning curve when you first start using it. Moreover, configuring workflows, permissions and issue types requires a lot of time and knowledge about the software. Our team hired a consultant to have everything perfectly setup for us.

Tracking software development would be impossible without great search. Jira excels in search. Usually, I can find the tickets I'm looking for by just entering in a few keywords. But when that doesn't narrow it down enough, the advances search capabilities are out of this world.

The thing that frustrates me the most about this software is the way it uses two different rich text editors—one for creating tickets, and one for editing tickets—and formatting between the two is not consistent.

Jira facilitates the management of software and application development activities. It is easy to report issues, bugs or other tasks adding them into the application backlog. Each report can be sort according to its priority and can be easily added to a specific sprint together with other tasks. Reports may be assigned to specific users and have specific status to be updated during the development...

Read more

You can’t assign a task to multiple users, only subtasks. It is not so easy to find information regarding mentions and comments related to single users except checking your emails.

I like that I'm able to track bugs and feature requests, and link them to the customer email so that I can stay organized and let the customer know when their request has been completed.

Searching for issues can be challenging.

- Nice blue theme that fits with color blind person like me. Clean and modern font is another plus - JIRA ticket has some cool graph show how many ticket have been processed vs. how many outstanding for the entire lifespan of the project - JIRA wiki can export to Markdown for other kind of publication

- I wish there was a better integration with editors such as VIM mode , or support to edit JIRA pages directly from Emacs. - Mobile app could be improved to take hand drawing and clean up pictures from dirty whiteboard - Needs a distraction free writing mode for Wiki pages.

The feature of Open DevOps that I enjoyed the most was its versatility. It gave me the freedom to adapt and adjust my infrastructure to meet my needs while enabling me to swiftly design, deploy, and manage cloud-based applications. Because to Open DevOps' open source nature, I had access to and control over the platform's source code, which allowed me to adapt it to my unique requirements. The platform also offers a vast selection of tools and services to facilitate and speed up development and operations. In conclusion, Open DevOps offers a practical and successful method for creating, deploying, and managing cloud-based applications.

It was a little tough for me to browse and the interface was a little perplexing. The resources and choices I required to handle my projects were hard to come by. I also thought the pricing structure was a little difficult to understand and a bit confusing.

I love the integration with bitbucket because I can relate commits, pull requests and branches to an amount os cards on Jira, what is great for maintenability as well as for management. We use a lot JIRA together with the clients, because it's a good tool for document requisites and to validate the flow of testing and creating functionalities.

I guess JIRA still need to improve their usability a lot. I believe that JIRA has a lot of functionalities that I don't use because I don't know how to and probably the feature itself was not easy to find. Another impromevent issue is the filter plugins. We've tried once to filter cards and subcards by epic and this was just impossible without an plugin. So, when we have an project's portfolio, we have to install a lot of plugins and consequently, this have some huge impact on performance.

Can manage a lot of work against many people and teams. Most people are familiar with it. Many integrations.

Not many bells and whistles. Not great the best UX but it works.

This gives us a lot of well respected integrated tools that allow us to really build our software projects with complete collaboration across the team

Sometimes it is a little difficult to find a feature or function. Eventually I find it.

It permits to write backlog for a project, then we can split it to sprints containing tasks. A task can be dragged to a different column state according to its progression, so that the team can have visibility about the task.

Jira contains many functionalities, so its getting started is difficult, and takes a long time to be familiar with jira.

The product simplifies the ability to attach design comps through the Envision plugin. There's not a lot of software that can do this seamlessly to coordinate between managers and developers.

Unfortunately this software has a very granular experience. This can be great for developers, but the many steps in the process of collaboration and completion can provide a steep learning curve to new project managers.

I like the availability and ease of customization more than anything. It is very easy to tailor Jira workflow to exactly meet your needs. I have been amazed at the sheer volume of available plug-ins that extend the functionality even further.

While it is hard to find anything to criticize about Jira, it can be a little bit intimidating at first. The very same amount of available customization that makes this such a fantastic product can also be a handful for a small team to initially set up and get running just the way they like it.

The Projects can be easily created, maintained and notified to the administrator and the groups about the status. One small update to the ticket reaches to the entire stake holders on the project. It reduces pain to update each one individually about my status

The Tool can be more interactive. For a Digital marketing guy like me, I have multiple tasks in a day, and recurring tasks too. When ever I update my tickets for the project, it always goes beyond 100%.