I use JIRA Service Management to provide access management and address any technical issues because it documents what we have done and how we have done it. I can check live past tickets to work on them, which is how I work with JIRA Service Management.

I use JIRA Service Management for our client support operations. Clients raise ticket requests from Slack, and the portal requests come to me in JIRA Service Management project, where I deliver assistance. I can check requests from emails as well, and clients can also create tickets. I have added several automations, making JIRA Service Management perfect for providing client support.

JIRA Service Management offers many valuable features, including automations for tickets such as automated responses and automatic workflow changes. There is also the option to integrate with Slack, which allows users to get responses there and create tickets from Slack or email. I can add fields to differentiate every ticket type.

JIRA Service Management impacts my organization positively because it is easy to use, and everyone is happy to use it. In service companies, everyone is familiar with JIRA, so my company also uses it, making it easier for new users to join and get support. It saves me time, and my experience with JIRA Service Management is very good.

JIRA automation simplifies my day-to-day work immensely. For example, if any access tickets come through Slack, I have integrated the API to automatically grant access to the user's Slack. These automations make my team's work easy.

I have saved time with the automation, and there are also automated responses to users which make my work easier. I set up workflows that enhance efficiency.

I do not feel any features are missing in JIRA Service Management that need improvement.

In automation, sometimes when I select fields, not all fields are available, which can lead me to create a complex JQL query. However, I receive help from the support team to resolve these issues.

There are no other improvements needed for JIRA Service Management that I have not mentioned.

I have been using JIRA for five years, and I have exposure to applications like JIRA Service Management, the main products, JIRA Product Discovery, and JIRA Assets and Confluence. These are all the Atlassian products my organization is using. JIRA Service Management offers many functionalities for client support, so it is very good to use.

JIRA Service Management is stable for my needs; I have not encountered any issues with reliability.

JIRA Service Management's scalability is excellent; I just need to submit an email to indicate how many licenses I want.

I have reached out to customer support whenever I face an issue in JIRA, especially when creating any automation. My experience has been great; I receive responses, but sometimes it results in wasting time.

I am not using any other solution before JIRA Service Management.

While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience.

I evaluated Zendesk, but JIRA seems perfect for my needs.

My advice for others looking into using JIRA Service Management is to go for it. I would rate my experience with JIRA Service Management a 10 out of 10.