Good afternoon,
We are currently facing an issue with automation. Let say we have an issue type named "Project" and an issue type named "Epic".
- The 'Project' is a parent of 'Epic' (with issueLink Parent of).
- We have 3 fields: Priority, Component/s, Fixversion/s
We create a Project with the 3 fields filled out. Then, we create the child of the project (= Epic): The Epic takes all the information from the Project (Priority, Component/s, Fixversion/s).
When the Project update a field, the Epic should also be updated. HOWEVER, sometimes the child will have different information from the parent.
Meaning, the Epic can have a different FixVersion/s from the parent. So, if the Priority is updated on the Project, the Epic should only have its field 'Priority' updated not: Component/s and Fixversion/s.
What we currently have with Automation Rules:
- When value change for Priority, Component/s, Fixversion/s
- If it matches Project
- For Linked issues (parent of)
- Edit issue fields
- Priority, Component/s, Fixversion/s
With this process, if ONE field is updated for Project ALL the field are updated for Epic.
What I thought could be possibly done:
- One automation for each Field
- (!) we have X fields to copy
- (!) we have 3 levels of (parent of/child)
- => hard to maintain
- Have a condition that knows "Priority has been updated less than 1mn -> so you can update the Priority"
- Could it be possible with JSON??
Thanks for your returns and ideas.
Regards,
