Jira Automation - combining costs in one epic

[Noah Müller]

Hey,
I need your help for my Jira project. In the column: "Costs", I would like to have all costs of the respective subtasks to be displayed collectively in the associated epic (see attached image). I wanted to solve this with Jira automation, but it doesn't work. How would Jira Automation have to be set up in detail so that all costs of an epic are summarized in the list? My current status of setting up the automation can be seen in the appendix.

Thank you!

[Trudy Claspill · Accepted solution]

Hello @Noah Müller 

Welcome to the Atlassian community.

I recommend that you change this portion of your Automation Rule.

Keep the first step "Fur: Ubergeordnet".

Immediately after that, before the next step, add to the branch a Lookup Issues action. In it provide a JQL statement to search for all the child issues of the Parent issue.

In the Edit Issue action you can then use the "sum" function to get the total of all Kosten values from the issues found by the Lookup Issue action, and assign that value to the Kosten value in the parent issue.

In my example the field name is "A number field" rather than "Kosten".

[Noah Müller]

Thank you, how could I open the number field for the last one ? 

My current status of setting up the automation can be seen in the appendix. I dont find the number field. 

[Trudy Claspill]

Hello Noah,

Use the pull-down field to find your number field.

Type in the name of your field and it should appear in the list of fields below.

Check the box next to the field. That will not close the list, because Jira is leaving it open in case you want to select another field, so click somewhere else in the Edit Action dialog to close the window. That should leave you with the Edit Action looking similar to this: with the name of your field (1) and a box for specifying the value (2).

Type the smart value into (2).

[Noah Müller]

Hey, thank you again. I still get a notification that it failed. Could you imagine because of what? You see all details in the appendix

[Noah Müller]

Some more details for the specific sections 

[Trudy Claspill]

The message is indicating that the automation rule has found your system to have multiple fields with the same name "Kosten" and the same field type. It doesn't know which one of those fields you are trying to update.

You will need to get the unique ID (i.e. customfield_12345) for the "Kosten" field in the project you are working with, and use that ID where you have used "Kosten" in your smart value. The following article explains how to get that ID:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

You will likely also need to update the field using Advanced JSON Editing, found by clicking on the "More Options" link in the Edit Issue action, rather than by picking the field from the list. This article explains Advanced JSON Editing:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

[Noah Müller]

Hey, I solved the problem with the field: Kosten. There is another problem with the "Lookup-Vorgang" and "Übergeordnet". Which components I have to change?

Best regards 

[Noah Müller]

[Trudy Claspill]

In the JQL try substituting Parent for Ubergeordnet.

[Noah Müller]

I dont know which one I have to choose for the JQL. I cant find something like substituting parent. Could you please help me? 

[Noah Müller]

[Trudy Claspill]

In English the field name is Parent. Try this for your JQL.

Parent = {{issue.key}}

On your instance you have set the language to German and some field names appear to have been translated. Ubergeordnet appears to be the translation for Parent. I have worked only with systems set up for English so I'm not sure if JQL would require this field name in English or German. German didn't work so I suggest that you try the English field name.

[Noah Müller]

Thank you! Without changing language it finally works. I used Parent and instead of: Übergeordnet --> Epic. 

[Hannes Obweger - JXL for Jira]

Hi @Noah Müller

welcome to the community!

I trust that you will be able to resolve this in Jira Automation!

Just as food for thought: If you're open to solutions from the Atlassian Marketplace and/or don't want this to eat into your automation budget, there's also a number of apps available that can help with this.

As an example, this would be easy to do using the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

With these, you can build a view like this in just a couple of clicks:

This is really just one of a virtually endless number of possible views and reports - you can also view, group by, and sum up any other field(s), configure different sum-up styles, etc. etc.

Any questions just let me know,

Best,

Hannes