What is our primary use case?
As a customer support representative or a customer engineer, my main use case for Jira involves issuing Jiras to other teams where customers present or reach out to us with certain issues related to our product. When I was working at another company as a quality engineer, I also had experience managing templates and adjusting them as I was primarily working on issuing bugs in the scope of product testing.
I created a recent Jira ticket after speaking with one of our engineers as we were receiving a lot of similar reports of the app crashing, and after looking everything up in Sentry, we understood that there is indeed an issue with the app. We have a board in Jira for customer requests where I created the issue, and it was duplicated in our web team's board as an official bug. That was the most recent case where I have used Jira.
What is most valuable?
The best features that Jira offers include the ease of tracking everything. I love Jira dashboards where you can track the data that you are interested in. I love the agility of the board management and the possibility of adjusting all the templates per board. Overall, I think it is a very useful tool for teams to be on track and to be on the same page. For example, if I am out of the office for a couple of days and then I return, I have easy access to understanding what has changed since I left and what the news are.
In my past experiences, I was the one creating dashboards for the issues that our team created, which helps us with our day-to-day operations. The reason that it is very important to us is because it gives a one-stop-shop to all the team members to be on the same page and decreases the chance of creating any duplicate tickets. It makes sure that everybody is on the same page, and we use it on a weekly basis to sync and inform our teammates about the new issues that we have raised.
Jira has helped not only our organization but many organizations to be very focused and understand what needs to be done and to prioritize things effectively. The board that I am speaking about, as far as customer issues are concerned, is a fairly new concept in our company because prior to that our escalation flow was just a written escalation in Slack and the communication there. Now it is more focused and aligned with the team because we do not take resources from the engineering and QA team. We just issue the report once we make sure that it is actually a bug, and it gets handled. This has helped save time and make everything more manageable and more focused.
I would recommend Jira for scalability as well, considering its ability to be extremely customizable and to meet any team's needs. I have used Jira in a team of ten people and in a team of five thousand people, so I consider this a very scalable tool.
What needs improvement?
It is really hard to say right now how we can improve Jira because it is already in a very good place. I think it comes down to the customization that is applied to each team, which Jira allows all the teams to do based on their pricing plan. There is not much that I think could improve, other than maybe a better integration with Notion because with Confluence, you have great integrations in Jira and are able to pull out data directly from Jira, while in Notion, it is a bit limited. A better integration with Notion would be very helpful.
For how long have I used the solution?
I have been using Jira for about five years since I started working in IT.
What do I think about the stability of the solution?
I have not experienced stability issues with Jira.
What do I think about the scalability of the solution?
I have not experienced scalability issues with Jira.
How are customer service and support?
I have had the chance of reaching out to their customer support a couple of times, and my experience has overall been very positive because they usually reach out within one to two business days and give specific answers.
How would you rate customer service and support?
How was the initial setup?
I have not been involved with the setup process in this company. However, as part of my previous roles where I was making some adjustments to our existing boards, I started trials with Jira to try to replicate something in my trial board and then to copy it in our existing boards. Everything was very straightforward. I created free accounts and was able to do everything that I would be able to do in my organization's Jira. Other than that, I do not have much experience with this.
What other advice do I have?
Using templates in specific Jira boards helps us save time by ensuring that all the tickets have the same structure and include the same relevant information that will help relevant teams. For example, in my previous experience for bugs, we had specific templates that had to be followed up. Different people from different departments were creating issues which were easily understandable by QAs. Having worked as a QA myself and using Jira, I can assure that it saves a lot of time by having these templates and knowing what needs to be filled in and what does not need to be filled in, while communicating this with our project manager to make adjustments to our template. If I receive any bug report from our customers, I try to reproduce it first before I issue a Jira ticket or before I even reach out to our QAs, which basically gives them more time and takes less time from them to confirm whether it is expected behavior or a bug. I create the bug, and using automations, I create a bug in our customer-specific board, which gets duplicated in our web or app board where it gets verified by the QAs.
My advice for others looking into using Jira is to make sure that you customize it to your needs, as it is extremely customizable. Using it out of the box might seem very hectic and not particularly useful for your use case, but making sure that you customize it based on the boards, templates, and other elements, and have all your relevant data in your Jira dashboards is extremely useful. Try to find ways to incorporate Jira into tools that you already use, such as Slack, Confluence, or something else, as it will be very helpful to stay consistent across the board.
I overall recommend Jira to any teams that are working on software products as it makes everything easier. This can be used by marketing teams and sales teams who are trying to reach out to different customers or who have a big project to manage, so it is a great project management tool. I would rate this product nine out of ten.