Page History

Versions Compared

Old Version 9

changes.mady.by.user Rebecca Plattner

Saved on Nov 06, 2024

compared with

New Version Current

changes.mady.by.user Julian Riedinger

Saved on Nov 15, 2024

Key

This line was added.
This line was removed.
Formatting was changed.

UI Text Box

size	medium
type	info

Use case

In our Jira Service Management project, we want to automatically add the reporter of an incident to the corresponding problem ticket incident's reporter as a Request Participant when Participant on the related problem ticket is moved to done.once the incident is marked as "Done."

UI Text Box

color	light-yellow
icon	tip

Prerequisite

You must be using To enable this functionality in Jira Service Management to record incidents. You must have a Jira Service Management Project with a Problem Ticket and Incident Tickets that are linked to that Problem Ticket by an , a dedicated project must be created specifically for recording incidents and tracking related problems. Each incident ticket should then be linked to its corresponding problem ticket using the "is caused by" relationsiprelationship. This link ensures that incidents are directly associated with their underlying problem. In addition, the ticket types must include the custom field Request Participant field must be available on the edit screenIncident and Problem ticket edit screens. This field allows participants to be added to receive updates on the ticket. The custom field code for Request participants is 10040 and will be used later.

Configuration steps

UI Steps

UI Step

Get started and set the issue to be updated

Add the post function Update fields to the transition of the Done transition . To update the problem of the incident workflow. As we would like to update the Request Participants of the problem ticket, we need to identify the issue to be updated. To to this, we choose as the target issue a parser expression. Here we use the linkedIssues() function to point to point to the Problem Ticket, using the same function that linked the Incident Ticket to the Problem ticket. follow the link torwards the problem ticket, that was already set previously.

Code Block

title	target Target issue -> Parser expression

%{linkedIssues("is caused Byby")}

Tip
Use the Fields required or changed validator to ensure that the required field is set.

UI Step

Add the request participents to the problem ticket

To add the request participents click on Add field and choose Request participants.

Value*

Set Value→Set field value manually (parser expression).

To add the request participants participant to the problem ticket , you need to combine the list of request participants from the problem ticket with the new participants using you must use the append() function to ensure that you do not overwrite the existing request participants. First, use the the fieldValue(%{issue.cf10040},linkedIssues("isCausedByis caused by")) function. Here,fieldValue() accesses the custom field for request participants, and in the second step, the the linkedIssues("isCausedByis caused by")function references the linked parent problem ticket. In addition, the toStringList(%{issue.reporter}) function retrieves the request participants from the Incident Ticket incident ticket and gives returns the reporter as a list's account id.

Code Block

title	Add field -> Request participants -> Value

%{append(fieldValue(%{issue.cf10040}, linkedIssues("isCausedByis caused by")),toStringList(%{issue.reporter}))}

Expand
title How to get a custome custom field code
Simply click Add field and search for Request participants within the expression parser to find the correct custom field.

Image Modified Related Examples

Page properties report

firstcolumn	Use case
headings	JWT feature, Workflow function, Parser functions, Complexity
sortBy	Title
cql	label = "use-case" and space = currentSpace() and ancestor = "38569498"

Page properties