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

Automation Rule to update a field to be the same as another field

Emna Elleuch

Is there a way to add an Automation Rule to edit a Field to be similar to another field which is available in another Issue type.

let's suppose i have 1 Story linked to an Epic, and i'm logging my time under that Story, so i would like to add an Automation Rule: Whenever the Time spent field in the Story is updated, i would like to see the updated time spent in the Epic too. Thanks in advance

Accepted answers

Trudy P Claspill

Hello @Emna Elleuch

When you say the story is "linked" to an Epic, do you mean it is listed as one of the Child Issues of the Epic?

What problem are you trying to solve by updating the Time Spent information on the Epic when the Time Spent information is updated on child issues?

The Time Spent field in an issue is updated by using the Log Work function to log time spent working on an issue. It is possible to create an Automation rule that detects that the Log Work function was used, that it was used on a Story, and then execute the same Log Work function against the story's parent Epic.

All comments

Trudy P Claspill

Hello @Emna Elleuch

When you say the story is "linked" to an Epic, do you mean it is listed as one of the Child Issues of the Epic?

What problem are you trying to solve by updating the Time Spent information on the Epic when the Time Spent information is updated on child issues?

Emna Elleuch

Yes it's listed as Child, Story=Child, Epic=Parent

I'm logging my time into the Story, and I Would like to copy this time to the Parent (which is Epic) so I can use the Clock Work App.

Trudy P Claspill

You could construct a rule that uses the Work Logged trigger to catch when work is logged against an issue.

Then a Condition to check that the issue where the work was logged was a Story.

Then a For Each / Related Issue / Parent branch to change the focus from the child story to the parent Epic.

Then within the branch use a Log Work action to log time against the Epic issue. You can reference information from the Work Logged trigger using the {{worklog}} smart value, as described in the information about the trigger.

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