🧩 Jira Service Desk Workflow Examples

Edit issue to select and change a field in your issue, like assignee or priority, as well as Jira supported custom fields (see Jira administration > Issues > Custom fields). Send email to create an email notification. Transition issue to change its position in the workflow. Webhook to send a POST request. Comment edited: Issue matches a certain One set of tools. Jira is at the center of Aeria Games’ work processes. All departments use it, even though the level of adoption is quite different. Radek’s team has begun to set up workflows for other non-technical teams, too, including HR. To continue improving, they have a group of volunteer employees called the Jira Jedis and the Idea: Ways to achieve: Assign new requests to the correct resource, based on information submitted. Use the built-in component routing feature to assign issues to the designated component lead.Use the built-in feature in Jira Service Management Cloud, or a marketplace app in Jira Service Management Server and Data Center, to change the request’s assignee based on desired criteria. If you copied the system workflow and you wish to rename the workflow transition buttons on the View issue page, you must delete the following properties from all transitions in the copied workflow: jira. i18n. title; jira.i18n.description; Otherwise, the default names (i.e. values of these properties) will persist. Read more about transition Just my idea, by using sub-task. Create new issue type (use sub-task issue type, you can give the name for this issue type) and define simple flow contain status waiting approval, approve, reject. in parent ticket, if you need approval create sub-task from above issue type and assign to approver. if need 2 approver, create 2 subtask, if need 3 Configure, maintain, enhance and upgrade the JIRA Software, Service Desk, Confluence and related Add-In components Work with business users to enable custom workflows, fields, dashboards, and reports Create and manage complex components including project workflows, screen schemes, permission scheme, and notification schemes Additionally, these are available for Jira Service Desk transitions: customerRequest (CustomerRequest): The customer request that is about to be transitioned. serviceDesk (ServiceDesk): The service desk the customer request belongs to. Validator example. The following example declares a validator for a transition. Next-gen Jira Service Desk is still in early access mode. With all the added functionality, the Change Management module in Jira Service Management now enables users to do the following: Deployment Tracking - Automatically generate Change Requests in Jira Service Management when a deployment is run using Bitbucket Pipelines, Jenkins, CircleCI In the issue view, in a "Service Desk" project, there is an "Approvals" section which shows the "rules/current status" for an issue. This is great for new "Service Desk" projects, but I want to have this as part of my JIRA Software projects. What I learned about applying the workflow scheme to JIRA Software projects: Customer Portal. JIRA Service Desk pre-configures a Customer Portal for each service desk you set up. The Customer Portal is where you design the request forms your customers will fill out. As the service desk manager, you can map the JIRA features that are used to manage each request to the user friendly language your customers will see. Tip Cb4O.

jira service desk workflow examples