JIRA Service Management Reviews

We are a management warehouse that provides services to different customers in different sectors. Primarily, we serve the banking sector and the military sector. We manage all the software delivery projects through tools such as JIRA Service Management or TFS.

Confluence is a great tool for documentation and tracking. Additionally, Bitbucket is essential for controlling the source code. JIRA itself is valuable for managing tickets, user stories, and pipeline. The integration between different tools provided by Atlassian products is also significant.

We use it primarily for test case management and raising bugs. It is a centralized tool that we use to track test cases, integrate with automation, and manage bug fixing.

The most valuable feature of Jira is that it is free of cost, which is a significant advantage. Bug raising is easy, and integration with other tools is straightforward. 

The centralized feature allows us to track test cases and integrate with automation and bug fixing.

Basically, I am creating JIRA tickets, querying JIRA tickets, updating JIRA tickets, creating views for all the JIRA data.

The query language and the ability to create views of the data are very useful. I can organize JIRA and set up tickets related to the projects I'm working on. It simplifies and accelerates my ability to manage tickets assigned to me or those I'm working with.

The dashboards are a good feature. The ability to actually edit dashboards is good. I can add modules into the dashboard to build out a sort of API, which is good. These capabilities are positive. Navigating around it is okay. A good example would be Visual Studio, which has an integration with Git.

My primary use case for JIRA is to track tickets while working in an agile mode. I use it during each sprint to keep track of all my team members. All the data is there, which makes it easy to analyze at the end of the year and evaluate what we have accomplished.

Using JIRA simplifies tracking issues and updates. It allows me to assign tasks easily to colleagues. This way, I don't need to set up meetings for every issue since there is a discussion space in JIRA. It is beneficial if someone is on vacation sincew others can follow up on the tickets.

I'm currently using JIRA Service Management for project management, specifically for communication with different tech tools and providing services for our product. It is mainly used within the research and development department, governed by product managers and service managers in operations.

It provides real-time updates to all the stakeholders, which is the best aspect of the service. It offers the opportunity to create customized communication and service tracking, allowing for more precise real-time changes.

I am primarily using Jira Service Management for sprint management, estimations, planning, pre-planning, and conducting all the sprint ceremonies with user stories and estimations.

It's commonly used, so we don't need to teach anyone. Any new member that joins knows Jira Service Management.

For every project planning, we divide each project into different epics based on the milestones. Then for every epic, we create stories and tasks to complete within a two-week sprint cycle. After the two weeks, we have a review session with the clients to showcase our progress. That's how we are doing it.

The tool is scalable. It is not mainly about administrative efforts, however, as a working user, it is easier to create multiple stories and epics. For every task we are working on, the project manager can see the status once we update the stories mentioned. It helps overall project management to understand what the progress is and if there are any blockers.

We use JIRA for user support, specifically first-level user support. 

Additionally, we use it to plan project steps. With the Carbon dashboard, it is possible to break the project into multiple steps. You can review what is done, what is set to be done, and what has been completed during the predefined time slots. For ITSM processes, we primarily use it for access processes. 

We also utilize its automation capabilities, such as automatically creating JIRA tickets from monitoring tools during batch execution errors.

JIRA allows us to easily monitor what the team is doing and which subjects team members are working on. The dashboard feature enables us to see task statuses and facilitates task management through drag-and-drop functionality. This has improved our productivity by making it easier to track tasks and team activities.