How to set stories parent field with Epic?

Jouni Riimala
Contributor
January 19, 2024


My Issue structure:
Epic - Requirement (system requirement / user requirement) - Story

I have rule, which summarize Story Estimation values (from story issues) to Epic (Estimate field) & this works. However, if in my stories I don't have Epic in the Parent field then it doesn't work.  

Question: How to construct the rule, which ensure if Epic child (ex. story) doesn't have value in the Parent field then it automatically set Epic to child issue (Story) Parent field?

My current flow:

 

Epic to story parent field.JPG

 

 

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2024

Hi @Jouni Riimala 

Just following up to ask if the suggested answers solved your question.  If so, please consider marking this one as answered to help others find solutions to similar needs faster.  Thanks!

If not, please explain what is not working as you expected, and post images of your complete rule, the details of the actions, and of the audit log details showing the rule execution.  Those will provide context for the community to offer ideas.

Kind regards,
Bill

0 votes
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 19, 2024

Please take a look at @Bill Sheboy answer below

https://community.atlassian.com/t5/Jira-Content-Archive-questions/Automation-I-am-looking-for-a-way-to-sum-Story-points-for/qaq-p/1647852

At a high level, under your branch, you need to do a look up and gather all issues so you can sum up their points.. There is also a youtube post in that thread which I havent looked but may be of help to you.

Jouni Riimala
Contributor
January 19, 2024

Hi,

Thanks from the link, after few modification got it working.

However, solution requires that Epic name (looks like it's Epic summary field value) is assigned to the Story manually so wonder how to set it automatically.

Any guidance within this would be highly appreciated. Willing also to create another rule, which check Epic issuetype using contains link role, which would then set child parent according epic. Current difficulties are within copy field value from the parent and assigning it to the story.

My current flow looks like this.

SummingStoryEstimations.JPG

Jouni Riimala
Contributor
January 20, 2024

To make things even more difficult structure is like this Epic - Requirements (system requirement / user requirement ) and then Story so wonder how to get parent from epic to story.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events