Jira Ticket Key

[Kathrine Selvage]

Howdid we get here? We created Jira Service Desk in 2013, after we noticed that nearly 40% of our customers had adapted Jira to handle service requests. Thousands of teams managed requests through service desks, reduced manual effort, and set up workflows across their organizations in departments like HR and legal.

Triage, track, and assign incoming requests from various sources with queues and SLAs. With conversational ticketing, employees can seek help directly from Slack and agents can track all the information they need in Jira Service Management. Gain full context on customer needs through linked issues and associated Insight assets.

Make it easy for every team to spin up a service desk. Showcase services through a simple, intuitive portal that makes it easy for your employees and customers to get help quickly, and for your teams to streamline incoming work.

Bring together requests from email, chat tools, your service desk, and other channels. Configure queues to track, triage, and assign incoming requests. Group similar tickets and make it easy to categorize service requests, incidents, problems, and changes.

Empower customers and employees to find answers to common questions using a self-service portal. Users can use the knowledge base inside Jira Service Management to surface relevant articles to deflect requests. They can get the help they need, without having to engage with an agent.

Set as many SLA policies as needed to keep track of deadlines based on elapsed time or request categories. Resolve requests based on priorities, and use automated escalation rules to notify the right team members and prevent SLA breaches.

Jira Service Management chat users can create a two-way sync between conversations in Slack or Microsoft Teams and Jira Service Management. Employees never have to leave Slack to get the help they need, and agents get all the information they need right in Jira Service Management.

Don't lose track of conversations with your customers. Move conversations from your inbox (or from Slack or Microsoft Teams with Halp) to queues in Jira Service Management so nothing slips through the cracks. Get from conversation to resolution in no time.

Integrations within the Atlassian platform link requests across a comprehensive digital pipeline, spanning planning, collaboration, task management, and product development (utilizing Jira and Trello), extending to continuous delivery (with Bitbucket) and knowledge organization (via Confluence).

Through automation capabilities and prioritized queues, Jira Service Management ensures that critical issues are addressed promptly, enhancing agent productivity and customer satisfaction. Furthermore, its integration with a knowledge base and self-service options empowers users to find solutions independently, reducing dependency on support teams.

By offering a robust suite of features, including ITIL-certified processes and extensive reporting and analytics, Jira Service Management enables businesses to deliver exceptional service while optimizing costs and resources. Whether tracking tickets, managing service requests, or enhancing agent productivity, Jira Service Management provides the tools and capabilities to streamline operations and drive business success.

Companies need an automated ticketing system to manage and track various service requests, incidents, and issues from customers, employees, or other stakeholders. Ticketing systems provide a structured framework for capturing, prioritizing, and resolving these service requests, ensuring timely and effective responses.

They also facilitate communication and collaboration among support teams, streamline workflow processes, and enable businesses to meet service level agreements (SLAs). Additionally, ticketing systems often include reporting and analytics features so businesses can gain insights into support operations, identify trends, and make data-driven decisions for continuous improvement.

Yes, ticketing system software is commonly used by IT teams to manage and resolve various IT issues, such as technical problems, software glitches, hardware failures, and service requests. It provides IT support teams with tools and features to efficiently handle incoming support tickets, prioritize tasks, track issues, and communicate with users. Additionally, desk ticketing system software often integrates with other IT management tools and systems, further enhancing IT service delivery and support processes.

While ticketing systems focus primarily on tracking tickets and resolving individual incidents, IT Service Management (ITSM) encompasses a broader set of practices and processes for delivering and supporting IT services.

ITSM goes beyond automated ticketing systems by incorporating service strategy, design, transition, operation, and continuous improvement activities to align IT services with business needs and enhance overall service delivery. ITSM frameworks, such as ITIL (Information Technology Infrastructure Library), provide guidelines and best practices for implementing ITSM processes, including incident management, problem management, change management, service and desk management, and more.

By adopting ITSM principles and leveraging integrated ITSM platforms, businesses can optimize service delivery, enhance user satisfaction, improve agent productivity, and drive business value through effective IT service management practices.

Incident tickets: Incident tickets are created to report any unplanned interruptions or reductions in the quality of IT services. These could include system outages, software errors, hardware failures, or network connectivity problems. Incident tickets are typically prioritized based on their impact and urgency to ensure timely resolution and minimize disruption to business operations.

Service request tickets: Service request tickets are created to request access to predefined IT services, information, or resources and have a standardized process for fulfillment. Examples of service requests include account creation, software installations, password resets, equipment provisioning, and access permissions. Service request tickets help streamline and standardize the delivery of IT services, ensuring consistent and efficient handling of user requests.

Change request tickets: Change request tickets are created to propose, review, and implement changes to IT infrastructure, systems, applications, or services. Changes could include updates, upgrades, patches, configurations, installations, or decommissioning. Change request tickets undergo a formal change management process to assess the potential impact, risks, and benefits of the proposed changes. This ensures they are properly evaluated, approved, scheduled, and implemented with minimal disruption to IT operations and business continuity.

Our requirements live in Confluence and then transferred to JIRA tickets. We see JIRA as our "source of truth" if you will, wanting to know if anyone knows of a feature that allows the updates made to a particular ticket in JIRA to update the requirements doc in confluence. Thanks in advance!

"We will have a confluence page setup that is based on a JIRA project. Basically, a compilation of all the tickets on a confluence page and we want to keep on updating the Page per updates on the JIRA ticket.

Absolutely! I'll set the scene for you. I'm demoing a new feature to my boss and wants an adjustment made. So I can have my dev start in it immediately I go and update the JIRA ticket they're working from to reflect the change. I then have to go update our decision log (which is fine) and update the supporting requirements doc in Confluence.

This may not sound like a lot but it can get out of hand quickly because of the size of the project so, I'm looking for a way to auto-update the requirements document with the changes I've made to the JIRA ticket. I figured this was a feature since Confluence allows you to easily transfer requirements into tickets with two clicks. Thanks in advance on any light you can shed :)

@Kim Lewis I know it's been a while, but did you ever figure out a solution to this? I know one way might be just to replace the entire page including the new content, but in my case, I'm looking for a way to change only some of the information.

I am trying to figure out a mechanism to move "Jira Software ticket" to "JIRA service Desk Ticket" So far, I have scanned many posts and have found some plug ins helps to convert the software tickets to service desk tickets. Not sure, if JIRA has any "Out of Box" feature for this.

This is supposed to be doable. I created a Smartsheet sheet that has all of the required Jira fields as columns. From the sheet I created a Smartsheet Form to collect all of these Jira fields. I then connected to our Jira instance with the Smartsheet Jira Connector and made sure the field mappings were bidirectional. No luck getting a new Jira ticket created. Smartsheet Customer Support suggested I reach out to the Community.

Hi @Jerry Smith - I am yet to test your question but in the meantime I found something that might help. Go through this link and let me know if you were able to get the resolution you were looking for.

People with a Smartsheet account that have activated the Jira Connector can create and sync Jira issues to Smartsheet. Individuals must be granted access to the Jira Connector by Smartsheet SysAdmins or Connector Admins.

I'd like to have a confluence page with a button or a link or (super great) a simple form that will begin the Jira ticket create flow with some fields pre-defined, such as the Jira project, and maybe Component, or a custom field or two.

Other questions like this in the Community have pointed folks to setting up Issue Collectors, but embedding an issue collector relies on embedding javascript in the page, which is not an option in Confluence Cloud, as far as I can tell. Also, that capability is a big security problem, so it's not ideal to make it OK, even if cloud allowed it.

3a8082e126