In one of my processes I have a multi-picket "Reviewer(s)" field. I'm trying to use a REST webhook to create a ticket for each person listed. I was able to: * Add a comment to the ticket using the automation * Validate the webhook and see the users listed in the custom field of my test ticket Now I'm stuck and can't find any good documentation on how to extract the users listed in the custom field and make new tickets. Can someone help?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create New Issues For Each User in a Multi User Picker Field Through Automations

Tom Scoggin

In one of my processes I have a multi-picket "Reviewer(s)" field. I'm trying to use a REST webhook to create a ticket for each person listed.

I was able to:

Add a comment to the ticket using the automation
Validate the webhook and see the users listed in the custom field of my test ticket

Now I'm stuck and can't find any good documentation on how to extract the users listed in the custom field and make new tickets.

Can someone help?

Accepted answers

Kalyan Sattaluri_iinm1n

Hello @Tom Scoggin

Please share what you have currently implemented as I am having hard time understanding the ask, especially where you have added a comment but I dont see that as requirement initially and not sure where you have added that comment.

Please correct below statement:

You have an existing ticket with multiple reviewers selected, you want to create new tasks (sub-tasks?) for each of them and assign to them?

All comments

Kalyan Sattaluri_iinm1n

Hello @Tom Scoggin

Please correct below statement:

You have an existing ticket with multiple reviewers selected, you want to create new tasks (sub-tasks?) for each of them and assign to them?

Tom Scoggin

Good morning,

My comment about an existing ticket is just to state that I have a sample ticket I'm using to test out my automation. I'm trying to create a new Story issues for each of the Reviewers listed in that test ticket. I can't figure out how to pull the data from the returned REST call and then creat the tickets.

Begining of REST Call.PNG

Kalyan Sattaluri_iinm1n

Hello @Tom Scoggin

Couple of things:

You dont need additional If condition after your scheduled trigger or a web request to get a list of reviewers.

You could give the same JQL in scheduled step itself and you can access the reviewers list directly using smart value.. {{issue.Reviewers}}

But, more importantly, because you are in Data Center edition, you dont have Advanced Branching to do For /Each to create issues for every reviewer found. So this is a limitation/blocker for you.

If you have a limited set of "Reviewers" then you can hard code them in If statements, such as:

If {{issue.Reviewers}} contains "Bob" -> then create issue for Bob..

You can add multiple such conditions given you know the list of potential reviewers.

Please let me know if this approach works and I can share a simple screenshot for reference..

Also, I can broadly share how to read your web request response but as mentioned, that is not needed for your use case because that information is already available to you.

Tom Scoggin

The list of reviewers is unknown so I can't do an If statement scenario.

I'm not sure how you can use the results of the smart value {{issues.Reviewers}} to create a set of new tickets. If that's something that can be done then I'm good with trying that. I just don't know how you would go about that. That's why I was trying to get the data from a REST call that brings them in.

I look forward to your response.

Bill Sheboy

Hi @Tom Scoggin

I believe Jira Server / Data Center can bulk-create issues using the REST API functions. If so, your rule could use list iteration over the values in the multiple-select user field to generate the JSON needed to add the issues, passing that to the Send Web Request action to call the function.

Kind regards,
Bill

Tom Scoggin

Thanks @Bill Sheboy.

This is my first attempt at using Web Requests. When I test my Send Web Request and give it a ticket number it returns the correct information. I'm not familiure with List Iteration. Where is that?

I think the smart value I will need is to create the new tickets is {{webhookResponse.customfield_10192.username}}. This is the response for Reviewer(s).

Bill Sheboy

Here is the documentation examples of iterating over lists: https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-examplesExamples

For your rule, you would iterate over the field values, adding the necessary JSON to create the issue. Example pseudocode of that would be:

{{#issue.yourCustomField}}

JSON to add the issue...referencing the user values when needed, such as {{name}}, {{emailAddress}}, etc.

{{/}}

I am using Jira Cloud, but I believe this is the reference for bulk adding issues with the REST API: https://docs.atlassian.com/software/jira/docs/api/REST/8.7.1/#api/2/issue-createIssues

Tom Scoggin

@Bill Sheboy I'm back working on this. I was able to create a Webhook and then get a list of Reviewer(s) and add them in the Audit Log. I'm trying now to create Story tickets.

I'm assuming I do it using the Create Issue plugin and then add my json under the Additional fields section.

I'm using this in the Create Issue Summary field - Review {{webhookResponses.body.fields.summary}}

When I try it now it's saying invalid json. Here is the code I'm using in the Additional fields section

{{#issue.customfield_10192}}
[
{
"fields": {
"customfield_11700": "{{webhookResponse.body.fields.customfield_11700.value}}"
"issuelinks": [
{
"type": {
"id": "10003"
},
"inwardIssue": {
"key": "{{webhookResponses.body.fields.issuelinks.inwardIssues.key}}"
},
}
],
"assignee" : {
"key" : "{{webhookResponses.body.fields.assignee.key}}"
},
"issuetype" : {
"id" : "10001"
},
"customfield_10101": "{{webhookResponses.body.fields.customfield_10101}}",
"creator" : {
"key": "{{webhookResponses.body.fields.creator.key}}"
},
"reporter" : {
"key" : "{{webhookResponses.body.fields.reporter.key}}"
},
"customfield_11340": "{{webhookResponses.body.fields.customfield_11340}}",
"description": "*Definition of Done:*The assigned Reviewer has reviewed """{{webhookResponses.body.fields.summary}}""" and worked with the author to correct any concerns.",
"priority": "10000",
}
]
{{/}}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk

jira-data-center

data-center