Comments
-
Marc's rule is a good starting point, but one update for current Jira: Epic Link is deprecated in newer company-managed projects. The current equivalent is the parent field: parent = {{triggerIssue.parent.key|"null"}} If your lookup returns zero results with Epic Link = {{issue.key}}, switching to parent usually fixes it.…
-
Michaela's solution is exactly right - filtering by status in the JQL lookup is the cleanest approach: parent = {{triggerIssue.parent.key|"null"}} AND status != Rejected One thing worth adding that isn't mentioned above: lookupIssues returns at most 100 results, regardless of how many issues match the JQL. If the epic has…
-
Trudy's pointer to {{fieldChange}} is correct. Here's a concrete rule structure that handles both the new and the old parent: Trigger: Field value changed -> Parent field Branch A - update the NEW parent: * Variable: newParent = {{triggerIssue.parent.key}} * Lookup Issues: parent = {{newParent}} * Edit issue…
-
For those asking about cross-item rollups (summing child issue values up to the parent) - you're right that formula fields don't cover this. Atlassian's own article states: "Formulas cannot be run across work items. For example, you can't roll up the estimated effort of all tasks to the parent using a formula field." The…
-
The Automation rule Paul outlined above is still the right starting point. Here's a consolidated version for anyone landing here fresh: Trigger: Field value changed → Story Points Action 1 - Lookup Issues: parent = {{triggerIssue.parent.key|"null"}} AND issuetype != Epic Action 2 - Edit parent issue: set your custom number…
