• Type: Bug
• Resolution: Duplicate
• Priority: Low
• Fix Version/s: None
• Affects Version/s: 7.1.1
• Component/s: Rule execution (engine)
• Labels:

  • iq-a4j

[JIRAAUTOSERVER-79] Support "Parent Link" fields

Collapse comment: Prashant Bagdia added a comment - 13/Sep/2024 7:51 AM

Prashant Bagdia added a comment - 13/Sep/2024 7:51 AM

Closed as it's a duplicate of  https://jira.atlassian.com/browse/JIRAAUTOSERVER-135

Expand comment: Prashant Bagdia added a comment - 13/Sep/2024 7:51 AM

Prashant Bagdia added a comment - 13/Sep/2024 7:51 AM Closed as it's a duplicate of   https://jira.atlassian.com/browse/JIRAAUTOSERVER-135

Collapse comment: Pietro Lemes added a comment - 09/Dec/2022 3:50 PM

Pietro Lemes added a comment - 09/Dec/2022 3:50 PM

Hello everyone, 

I don't know if this solution is applicable to all your cases, but I've made this KB describing a method to copy values from any "direction" without branching blocks, please give it a look:

How to copy custom field values to the trigger issue using the Parent Link field (without using branch blocks)

I would appreciate any feedback!

Kind regards,

Pietro Lemes
Atlassian Support

Expand comment: Pietro Lemes added a comment - 09/Dec/2022 3:50 PM

Pietro Lemes added a comment - 09/Dec/2022 3:50 PM Hello everyone,  I don't know if this solution is applicable to all your cases, but I've made this KB describing a method to copy values from any "direction" without branching blocks, please give it a look: How to copy custom field values to the trigger issue using the Parent Link field (without using branch blocks) I would appreciate any feedback! Kind regards, Pietro Lemes Atlassian Support

Collapse comment: Mykenna Cepek added a comment - 09/Aug/2021 10:09 PM

Mykenna Cepek added a comment - 09/Aug/2021 10:09 PM

I'd like to suggest that Automation could do much better at abstracting away the messy rule hardcoding of the "child/parent" relationships in the Jira hierarchy.

That messiness has encroached into Automation Smart Values in the form of "issue.parent" (for Subtasks only) and "issue.epic" (for Story-level issues only), for example.

One downside is extra complexity in rules which have to have separate "find parent" or "find child" logic based on the type of the current issue. Another downside is every automation rule writer having to learning the hard way that "issue.parent" does not work for Story-level issues. Another downside is the OP of this ticket.

Automation CAN abstract away the messy internals of Jira, and just present rule writers with access to a "parent" or "child" of any issue (across the entire hierarchy, including themes, initiatives, etc).

One of the promises of Automation being an abstracted layer over the Jira internals is simplification. The Jira hierarchy is in need of this simplification, as reflected in rules.

Expand comment: Mykenna Cepek added a comment - 09/Aug/2021 10:09 PM

Mykenna Cepek added a comment - 09/Aug/2021 10:09 PM I'd like to suggest that Automation could do much better at abstracting away the messy rule hardcoding of the "child/parent" relationships in the Jira hierarchy. That messiness has encroached into Automation Smart Values in the form of "issue.parent" (for Subtasks only) and "issue.epic" (for Story-level issues only), for example. One downside is extra complexity in rules which have to have separate "find parent" or "find child" logic based on the type of the current issue. Another downside is every automation rule writer having to learning the hard way that "issue.parent" does not work for Story-level issues. Another downside is the OP of this ticket. Automation CAN abstract away the messy internals of Jira, and just present rule writers with access to a "parent" or "child" of any issue (across the entire hierarchy, including themes, initiatives, etc). One of the promises of Automation being an abstracted layer over the Jira internals is simplification. The Jira hierarchy is in need of this simplification, as reflected in rules.