I have an automation that scans all items linked to an epic (regardless of the project they are in) and assigns the sum to a custom Epico field called "Plan estimate". This rule is triggered when the "parent" field of the child item changes. I need to increase this automation by reducing the story point total when a child item is removed from the epic (deleted or broken parent-child relationship).
Hi @Massaut
For a summing scenario like this, there are several cases to consider. Please consider and decide which ones you want rules to cover them, such as the following:
For your question, cases #3 and #4 apply...
Deciding how accurate the sums should be, and the impact on automation usage for the month, will influence your approach. Another approach is to use a scheduled trigger rule, which updates all epics once per day.
I recommend discussing this need with your Jira Site Admin to decide which approach to use for your team and company.
Kind regards,
Bill
@Bill Sheboy, I'm the global Jira admin here at the company. Our Jira is enterprise, so I don't have problems with the number of automations, as they are unlimited.
I really need help putting together the rule (when a child item is removed from the epic, to subtract the equivalent value of that item).
I can't create this rule, I don't know where I could be going wrong. I have a rule for whenever an item is assigned to the epic, I have a rule for whenever there is a change in story points on assigned items, but when an item is removed from the epic, the story point value remains there, unless otherwise history changes in the story points field, so the field is updated.
With this explanation, did understanding become better?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First, as you note being the global Jira admin for your company, I strongly encourage you to learn more about writing and maintaining automation rules. As your colleagues use the tool, they will need your support and you will want to ensure they do not cause harm to the site via rules. Perhaps seek additional training from Atlassian on rules.
Next, I recommend reviewing the documentation on the changelog smart value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--
With that smart value, a rule may detect the correct old / new epic.
Unfortunately...with the sunset of the Epic Link (and some other epic fields) still in progress, the replacement Parent field is not fully integrated for changes in rules yet. Until that is completed, this template rule could be used to access the issues via the Epic Link changelog:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After a few hours of trying, analyzing, reading and studying... I managed to make the scenarios I needed work, creating three different rules. Thank you very much for your help and encouragement in being able to resolve this on my own. It worked out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Massaut , Can you share your solution on how you were able to subtract points when a child issue was removed from the Epic?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kunal Dhir hello!
Of course! I will be happy to contribute to the solution.
Below are screenshots of the rule:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All, I am struggling with the change epic Rule as I am making all those rules to cover very similar scenarios as above. But seems this is not wokring. Any advice? thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please post an image of your complete rule, in one single image, and of the audit log details showing the rule execution. Those will provide context for the community to help.
Until we see those...
Please explain what is not working?
What you may be seeing is the Parent field replacement of Epic Link has not yet happened for the changelog in automation rules. Instead please continue to use the old field:
{{#changelog.Epic link}}{{fromString}}{{/}}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.