JIRA Service Management

The default settings for Jira Service Management allow you to maximize its potential right away, with nothing in the way of setup. It is possible to personalize it with a wide variety of settings so that it functions just how one would like it to.

Because our SSO implementation needs it, in order for a user to sign into the customer portal, they will first need to sign into the parent Jira site.

It is a slightly different tool from the so-called general ITSM system (or service). Operation and maintenance (though not limited to) tend to be individualized. Still, JIRA caters to tasks and support on a "role" basis, so sharing knowledge using OJT is possible, depending on ingenuity.

It may be a problem due to the multifunction, but I think the problem is that the screen is a bit hard to see. (The problem may be solved by changing the layout of frequently used functions, but I haven't used it much yet, so I think it will be a problem that will be solved as I use it).

Most important functions, from perspective of scrum or devops team member, can be learn quickly and used easily. Also it gives a lot of option of organizing workflow between many agile teams. You can have different levels of tasks - and visualizations to them. I like that you can organize many boards and link everything. It takes of course a little bit of consistency in following the rules in order to not create a mess.

Well, it tends to have sudden downtime.. for no reason (well at least from my perspective) it’s not responding. Speed interface could be improved. Sometimes you have to wait a while after an action performed.

- Powerful project tracking: it provides an extensive range of tools and features to effectively manage software development projects, including issue tracking, task assignment, and progress monitoring.- Customizability: The software allows for extensive customization, enabling teams to adapt it to their specific workflows and requirements.- Integration capabilities: it seamlessly integrates with various development tools and platforms, facilitating collaboration and enhancing productivity.- Reporting and analytics: it offers robust reporting and analytics features, providing valuable insights into team performance, project progress, and issue resolution.

- Steep learning curve: Due to its vast customization options, JIRA can be initially overwhelming for new users, requiring time and effort to fully grasp its functionalities.- Complexity: The extensive features and configurations available in JIRA can sometimes make the software feel cumbersome, especially for smaller, less complex projects.

I find the UI of Jira Service Desk very clean and modern compared to other service desks software on the market. Included with the service desk is a customisable user-facing portal for users to raise tickets in, which proved very popular with staff when raising tickets alongside traditional email tickets. Due to the way Jira splits service desks into different projects, we were able to create service desks for other departments in the organisation which helped improve productivity and workflow. There are some very useful and well-designed default reports included for ticket statistics (which can be used to keep management happy!). We found the default setup of Jira Service Desk fit our needs very well, but it is very easy to customise ticket workflows and other features to suit more complex needs.

For a service desk technician using Jira Service Desk the back-end UI for managing tickets can be a little overwhelming, however this can be fixed by editing the default workflows for tickets to hide not required information and details. The administration settings are somewhat unintuitively set out for system administrators, but once you get to grips with the layout it becomes easy enough to find what you need from the settings page. We found the instructions on the Atlassian website for setting up an external redirect with a custom URL in IIS a little sparse on detail, but a quick trip to the Atlassian forums cleared up any queries we had with the process.