Hi, I have a field "Risk" on Epic which is a choiceList with values Red/Yellow/Green. Epics will have some stories linked to it and story will also have this Risk field, which will be provided by user. For ex. An epic having 10 stories as child. * If Risk of all stories are "Green" then set Risk of Epic as "Green". * If at least one of the stories is "Yellow" them set Risk of Epic as "Yellow". * If at least one of the stories is "Red" them set Risk of Epic as "Red". Is it possible to implement this scenario using automation in jira

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; } } }

Autopopulate Field using automation

Omkar Rajale

Hi,

I have a field "Risk" on Epic which is a choiceList with values Red/Yellow/Green. Epics will have some stories linked to it and story will also have this Risk field, which will be provided by user.

For ex. An epic having 10 stories as child.

If Risk of all stories are "Green" then set Risk of Epic as "Green".
If at least one of the stories is "Yellow" them set Risk of Epic as "Yellow".
If at least one of the stories is "Red" them set Risk of Epic as "Red".

Is it possible to implement this scenario using automation in jira

Accepted answers

Dick

Hi Omkar,

In your case I would build an automation with a trigger on the change of content of the Risk field on issuetype stories. You can follow that up by saving the parent key and subsequently using lookupIssues with a JQL query that tests for the two conditions, being parent key and Risk = Green.

Rinse repeat for Yellow and Red

You can store the lookupIssues.size parameter in a variable each time, so it can be used to test your three test conditions and setting the parent epic Risk accordingly.

I hope you find this useful

Dick

All comments

Dick

Hi Omkar,

Rinse repeat for Yellow and Red

You can store the lookupIssues.size parameter in a variable each time, so it can be used to test your three test conditions and setting the parent epic Risk accordingly.

I hope you find this useful

Dick

You can only have one set of lookupIssues at a time, so make sure the .size parameter is stored before you go for the next lookupIssues query.

Omkar Rajale

Thanks a lot for helping. It was a little tricky, but it worked.👍

Dick

Hi Omkar,
If you post a picture of the automation, we're helping out people with questions similar to yours. Two flies in one stroke, so to say.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud