Hello Community,
I am following this article: How to create an automation rule to add story points to Epic. The program is executing successfully, but the story points are not being updated in the Epic's story point field. Can you please guide me? OMS-8247 is my Epic
Thank you!
Hello @Harsha Shridhar
What is the Story points value of the issue you changed?
What is the Story points value of the Epic when this rule finishes?
What do you expect the Story points value of the Epic to be when this rule finishes?
According to the log output the Epic of the changed issue has only one child issue - the one you modified. Does that match your expectations?
If there are child issues in both OMF and OMS then your rule Scope must be global/multiple projects so that the OMF project issues can be retrieved.
Hello Claspill,
Thanks for the quick response! Here are the details:
My Epic has two children: one as a sub-task and the other as an issue link. I am updating the user story field on both children, but it's not reflecting on the Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have ensured that multiple projects are added to the scope.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What are the details of your Create Variable action?
In addition, the article you referenced is for Jira Cloud, and it is apparent from your images that you are using Jira Data Center. The functionality of Automation for Jira is different between the two products.
In Jira Cloud sub-tasks cannot be created directly within Epics. There is a way to force it to happen, but it considered a bad practice. So, the referenced article actually does not include summing up information from sub-tasks.
Notice also that the results of your Lookup Issues action is just one issue, the child issue. The sub-task that is directly under the Epic is not included because the sub-task's "Epic Link" field is not set to the Epic issue key.
To get sub-tasks that are directly below an Epic in Jira Data Center you have to modify your JQL statement. I recommend that you test the JQL statement in the Issue Search screen with an actual Epic issue key to ensure you get the JQL correct to retrieve all the issues you expect. I don't have a Data Center instance where I can test the JQL, but I think you need to add one of the following:
"parent"={{issue.epic.key}}
"Parent link"={{issue.epic.key}}
You are also going to encounter a problem with this rule if the triggering issue is a sub-task. Your sub-task issue type appears to be named "Task", so the rule would pass the first condition checking the triggering issue's type. However, since sub-tasks don't have their Epic Link field set, the Lookup Issues action will fail because {{issue.epic.key}} will not have a value, I believe. I don't have a Data Center environment available where I can test this thoroughly.
You could make use of the Log action to write out to the Audit Log for the rule the values such as {{issue.epic.key} to see what information is actually available if a sub-task triggers this rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Claspill. I tried your suggestion of using the parameters:
parent = {{issue.epic.key}}
Parent link = {{issue.epic.key}}
The rule executes perfectly with both parameters, but the Epic story points field is not being updated with the value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What are the details of your Create Variable action?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Harsha Shridhar I was able to recreate this in the cloud, maybe you can try this? The ONLY big difference is that I used Parent instead of epic link since we don't have epic link in the cloud anymore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much, Ortiz. I am getting a syntax error; it's expecting a value for the parent issue key, or the smart values are not being populated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please post screenshots of the section of your automation rule that updates the Epic and we can see if we can troubleshoot it with you.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.