Open DevOps Reviews - Page 3

A great tool for Agile development. We are using it for production deliveries and I personally like it. Tracking ongoing developing, deliveries and going back to previous release, really awesome. Inbuilt feature to export items in excel so you can filter out and send to team membres. The one I really like is assignment. When a bug is assigned, all the parties are notified with all the udpates. this makes everyone to be on same page without any chain email and meetings.

The search feature in JIRA itself is not good. I personally have to type something in search field to bring search window and then I modify it. i was expecting dropdown based filtering on search but it doesn't have. Many configuration can lead to ovewhelming. Navigating around UI is something tricky and you need to know where exactly it is.

It is purpose built for managing software development. For that it it very well suited from stories to bug fixes in the life cycle. In devops, there are great integrations and strong capabilities for stand-up, deployment, upgrades, and changes in operations tied to triggerable events from JIRA. In an ops environment JIRA is a workable tool, but is not ideal. That said it may be worth compromising to have a single tool across the entire organization.

While JIRA is the go to tool for dev and devops, it is weak in an operations environment. Time tracking and assignment of tasks are highly manual. Queue view are customizeable, but difficult to manage at scale. Analytics are very very poor. I tried exporting data for analytics on DOMO. While I could get that to work, the process remained highly manual and therefore not a workable dashboard environment. JIRA tools, widgets, and dashboards are reasonably customizable, but again not purpose built for ops. For example, time tracking is not start/stop/context driven.

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.

Jira is becomming more and more popular. Together with Confluence, Github, Jenkins. it offer platform to manage the projects into a well-designed hierarchy. Keep tracks of the relationship between requirement, task, development , deployment and release. It integrated with Confluence for the knowledgebase. Github to the soucecontrol and defect tracking. Jenkins for the deployment. Big community are making it better and better.

I didn't like Jira at the beginning. While that was about 12 years ago. The recent releases are much more mature. Not too much to complain.

After trying quite a lot of progress tracking apps for teams this is the one I like the most. The design is really intuitive. And there's a lot of customizing options and ways to automate management processes.

Not that easy to set up and quite expensive even on standalone version.

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

Jira helps you gather all the information about your development progress in one place. You can create different types of issues like To-DO, bugs ,tasks and epics. You are able to circle through different boards depending on your project which opens up the door for supporting a good number of projects while on the same web app. There are many helpful features to each "Jira" you open in order to identify its importance, priority and who is responsible for tracking and solving that "Jira".

The cons are down to accessibility, ease of use, and readability. Many features that should be automatically found such as easier Advanced filter access when searching, or viewing boards more easier, ability to click save instead of saving automatically which send unnecessary notifications to users. Cannot place notifications on specific projects when new jiras are created.

Very customisable, server version great for installing in house, integrates well with other software such as Confluence. Fast and effective project and development management software. Excellent support.

Steep learning curve. Admin overhead too big in the end for a small team to keep core product and plugins up-to-date.

Excellent feature set and extremely affordable for small development teams. Easily setup Kanban or SCRUM boards, sprints and tickets for task tracking. For power users, offers a custom query language and tons of customization options to build a workflow that matches what works best for your team.

The only thing I disliked, was the inflexibility when it comes to attaching sub-tasks and bugs to existing tasks. AzureDev Ops supports an Epic->User Story->Task->Sub Task->Bug->Test Case. JIRA only supports 3 levels (Epic->User Story or Task or Bug->Sub Task).

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.

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.

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.

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.

- Tagging issues with epic names helps in tracking and better management of tasks. - Great integration with github so you can see commits and Pull requests. - can be integrated with apps like confluence, slack, confluence. - different stages to track issues like progress, review, production.

- Every time clicking on a link opens up in the same tab, there should be an option to setup open links in new tab. - tracking History of an issue UI is a little weird and can be improved.

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.

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

Anyone can generate report report , track issue , awesome application .I found a bug please go through whole fedeback.

Bug Found on JIRA :- When issue list/keys goes to beyond 2 thousand numbers (For eg:- Project Name issue Key :- SAG-2001) then on Extracted/Downloaded CSV Report on windows OS , that extracted report is missing with First 2 digits of Issue Key From SAG-2001 , it is displaying as SAG-01 ) For more details contact anuradhagawande862@gmail.com. or +917972699213. Let me know how much bucks i should get for this bug?

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.

Its been a few years since i've used Jira but after using other programs this one still stands out as the best. Easy to use, easy to track jobs and upload and great notification qualities. Can be used across the company from Creative teams to Development

I resisted using it for my team due to the fact that it looked too complicated but once our Dev manager ran thru it with me i saw just how easy it was to use.

It is a very good tool for project management especially tracking project steps at a very detailed level and workflows for the various steps in the project can be incorporated into this software. It also facilitates communication with the all the members involved in the project when configured. Helps devops environment very well.

Since this software can get into great granularity, there is a very steep learning curve involved for users to get started with this great product. While it takes time to train users and get them comfortable, once they are past the learning curve, they seem to really enjoy using this tool.

Broad range of functionality, and the amount of customization you can do with your instance of JIRA.

Adding features also adds to feature bloat and complexity.

The most likable things is we can post daily status report and organization can track the developers work. Developers can assign task to other developer or tester. Tester can approve task or reject task after reviewing the task. Client can give task and assign task to specific developer within organized manner. We can add our message or attach file for review of the task. We can upload the related task screens and task link to specific task. Multiple task can be create and assign to developers.

It is slightly tricky to use the software. It needs 2 - 3 days to be used to of it.

TONS of features. My team and I use this to manage our tasks for our projects. It’s helped us keep our tasks oraganized. We use the kanban board feature to move cards from one column to the next. Also have integrated it with concourse and slack to automatically pick up the ticket title from the done column to generate a list of done tasks and post them to Slack.

TONS of features. There’s so many features that it’s a bit overwhelming. Also some parts of the app can be glitchy. Not sure if the team is constantly pushing updates to the UI but sometimes I have to search for certain fields because it’s not in the same spot that I last saw it.