Automatically Add Incident Reporters to Problem Tickets

Use case

In our Jira Service Management project, we want to automatically add the reporter of an incident to the corresponding problem ticket as a Request Participant when the ticket is moved to done.

Prerequisite

You must be using 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 "is caused by" relationsip. In addition, the ticket types must include the custom field Request Participant on the edit screen.

Configuration steps

Get started

Add the post function Update fields to the transition. To update the problem 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.

target issue -> Parser expression

%{linkedIssues("is caused By")}

Add the request participents to the problem ticket

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

Value*

Set field value manually (parser expression).

To add request participants to the problem ticket, you need to combine the list of request participants from the problem ticket with the new participants using the append() function. First, use the fieldValue(%{issue.cf10040}, linkedIssues("isCausedBy")) function. Here, fieldValue()accesses the custom field for request participants, and in the second step, the linkedIssues("isCausedBy") function references the linked parent ticket. In addition, the toStringList(%{issue.reporter}) function retrieves the request participants from the Incident Ticket and gives the reporter as a list.

Add field -> Request participants -> Value

%{append(fieldValue(%{issue.cf10040}, linkedIssues("isCausedBy")),toStringList(%{issue.reporter}))}

Simply click Add field and search for Request participants within the expression parser to find the correct custom field.

Related Examples

Use case	Workflow function	Parser functions	Complexity
Add a sub-task's summary and key to the description of its parent	Update fields		BEGINNER
Add three days skipping weekends automatically to a Date Picker	Update fields	dateTimeToString() dayOfTheWeek() addDays()	BEGINNER
Add watchers from another field	Update fields Transition issue	union() toStringList()
Assign an issue to the project lead, if the issue is unassigned on creation	Update fields		BEGINNER
Assign an issue to the user who last commented on it	Update fields		BEGINNER
Assign important issues to the project lead	Update fields		BEGINNER
Automatically add incident reporters to problem tickets	Update fields	append() fieldValue() linkedIssues() toStringList()	BEGINNER
Copy field values from epic to issues under it after creation	Update fields Transition issue	epic() issuesUnderEpic() filterByStatus()	BEGINNER
Copy labels of a sub-task to the parent issue upon closing	Update fields		BEGINNER
Keep parent's priority in sync	Update fields		BEGINNER
Obtain the difference between two dates	Update fields		BEGINNER
Set a date field to a future date	Update fields	dateTimeToString()	BEGINNER
Set a date field to the current date	Update fields	dateTimeToString()	BEGINNER
Set Fix version to Affects version when resolving an issue	Update fields		INTERMEDIATE
Set the Assignee based on the Issue type	Update fields	getMatchingValue()
Set the due date based on the priority	Update fields	getMatchingValue()
Set the priority to Highest if the 'Infrastructure' component is selected	Update fields		BEGINNER