Jira Service Management

As said earlier, I liked the fact that we can integrate with Atlassian products and with other products and communication between teams is the star feature I liked the most and coming to the remaining things like ticket handling or assignment and automation and customizations, these are also the things I would say I liked them. Also, the main thing is the service portal, it is user friendly once we get used to it. This is also the one I liked the most as we can submit the requests and track them easily and this supports the teams to get up to date info and tracking. Also, one more attractive thing is the customization of flows, automatic assignments and reporting. These are also the standouts of this product which is Pro features for the IT operations as they typically deal with the reporting and clear issue assignments which reduces their workload and helps work better.

Strong integration between Jira and Confluence Highly customizable workflows, schemes & request types Love the automations & SLA tracking Finally good reporting & dashboards. Takes time to built but its worth it

The platform's ease of use provides for an intuitive and modern interface that lowers the barrier of entry for both the agent and end-users. This was a significant improvement from our previous ITSM provider. The clean user experience has encouraged adoption from outside IT to other parts of the business. For teams already deeply embedded in the Jira environment, the native integrations are a significant improvement, as it allows for a user endpoint to submit requests, but being able to work with filters, the teams dont have to change their workflow as Jira Service Management tickets can be brought to already existing Jira Kanban boards. Lastly, the powerful automation features from Jira Automation is extended to Jira Service Management, allowing for the creation of sophisticated, low-code rules that drive operational velocity and reduce our manual overhead.

I would say it is better for large teams, because for small teams we need the same complex initial implementation and setup as for large teams. Complex administration is what makes it somewhat difficult for the admins but on an overall the setup is worth the product usage. One more thing as mentioned earlier, it integrates with other products, but with Atlassian products strong integration is there but it is somewhat lacking with the outside product integrations. Although it provides vast integration support it finds it something missing int hat part. Also as mentioned previously the interface as someone who is a beginner they may find it difficult to understand once understood then as that is also mentioned it will be a great experience. My point in saying this is that the UI is not that intuitive to the user in the initial days. Also, as the organization grows bigger, the licensing cost grows too, but on a scale we can say it's worth the services to the cost of licensing.

Administration can get complex beyond the basic ones & would require specialized knowledge & training. Out of the box reporting is limited and requires additional plug-ins. Also, licensing can get expensive & there were price hikes recently

One of the main problems with JSM is the limitation of doing customization through the API, it restricts a lot of behavior that is needed to tailor the platform for the requirements set by the enterprise. This often forces us to look for outside solutions to bridge those gaps. Another frustrating trend is the deprecation of established features from previous versions, whether it's the API or main features. Removing such functional tools was integral to our workflow and created unnecessary tech debt that was additionally hampered by having to manually configure it due to the lack of API options. Lastly, when looking at problems other users have had, there are a lot of long-standing feature requests that stay unaddressed, leaving persistent glaring gaps in the product's core logic. Essential needs like missing the team field within JSM Dashboards make it harder to keep everything within Atlassian. They have been adding new features like the Assets Dashboard, but it needs to be more expansive and more versatile before being able to use the tools provided more willingly.