Any way to update fields on epics depending on related issues?

[Rosana Casilli]

Hi all!

I am working on a new project for OKRs in my company. It is just a demo.

So I have some epics in this project that represent OKRs and the related issues would help me to know which percentaje of the OKR is completed

To achieve that I have some new fields created where I set the quantity of related issues are Done and the quantity of related issues are still pending, and then another field to calculate the percentaje completed. 

The problem I have is that I want those values to be updated to the epic, and I have several epic in this project.

Right now, I have done the following:

but as you can see I have ask for a specific epic link name. I would like to do it dynamic, that this calculation is done for every epic in the project. 

Any Ideas?

Thanks in advance

Ro

[Trudy Claspill · Accepted solution]

Hello @Rosana Casilli 

Are you using a JQL statement in your Schedule Trigger? If so, what is that JQL?

Each action in the rule will be taken for each issue retrieved by the JQL you put in the trigger. If you use a JQL that retrieves just the Epics, then you can use {{issue.key}} where you have used OEI-1258.

You'll also want to uncheck the "Only include issues that have changed" option in the Trigger to get the recalculation to be done every time for the specified Epics.

[Rosana Casilli]

Hi @Trudy Claspill  in the JQL statement I was searching for all issues in the project.

Project = OEI

If I set in the filter issuetype = Epic when the rest of the automation is excecuted, is not retrieving the right issues. 

I have the checkbox "Only include issues that have changed" unchecked.

I need for each epic in the project to look for the related issues and calculate those values. 

What am I doing wrong?

[Trudy Claspill]

If you set the JQL in the Schedule Trigger to

project=OEI and type=Epic

...then that trigger should retrieve all the Epics in the project.

Your Lookup Issue actions would then need to use the following JQL:

"Epic Link" = {{issue.key}} and...

...adding your other criteria. That will find the child issues of each Epic.

I tested this in a Company Managed Software project where I have multiple Epics, some of which have child issues and some that don't.

You can use the Log action to output data that is being retrieved into the rule Audit Log to confirm you are getting what you expect.

If that is not working as you think it should, please show us the updated rule, the details for the rule execution in the Audit Log, and indicate in which step it is not doing the right thing. Provide the details of that step, and information about the relevant issues to demonstrate how it has not worked correctly.

[Rosana Casilli]

Thank you so much @Trudy Claspill  it worked!!!

[Oleksii Marynych]

Hi @Rosana Casilli

The point you're dealing with is something we've wanted to solve ourselves, so we've made OKR Board for Jira.

Our OKR Board for Jira plugin allows you to use Jira Epics and Issues as contributing Key Results. You can also set custom KR weights based on their business impact so they will contribute to the Objective completion percentage accordingly.

Check out our app, it may meet your OKR needs.
Anyway, feel free to ask me any OKR+JIra related questions. I'll be happy to help.