Calculated value shown in a different issue

[Nadine Arnold]

Hey,

I have a question regarding the calculation of fields. 

Situation: Every day we create issues for our teams where they can document their actual and planned headcounts (two numeric fields). These are in one project, all with the same issue type.

So I have for example these values:

- Team 1: actual 5, planned 7
- Team 2: actual 6, planned 6
- Team 3: actual 8, planned 9

What I would like to have is one (!) additional created issue based on the values of the teams. Also same issue type and project, but with a calculated actual and target headcount. When creating the team ones, the numbers of the day before will be set in the creation process. Later on I would like to add the function that as soon as a value is changed, the department value shall also be updated. But with the creation I would expect to see this numbers:

- Department: actual 19, planned 22

What works totally fine is to create the team issues with the numbers of yesterday. I added now the creation of the department issue, but I have no idea how to calculate and set the actual and target headcount. Could you please help?

[Nadine Arnold · Accepted solution]

Already found the solution by my own without restructuring what was already implemented.

I created a second automation, made a look up issues and used the {{lookupIssues.Target Headcount.sum}} function to calculate the value. Works perfectly

[Dick · Accepted solution]

Hi @Nadine Arnold 

Your best approach would be to schedule a daily creation of an story (for the department) with 3 subtasks (for each of the teams). 

A second automation would trigger on change of either count field in a sub-task, find it's parent and sum the two fields across all sibling sub-tasks of the parent work item.

Kind regards,

Dick

[Marc - Devoteam · Accepted solution]

Hi @Nadine Arnold 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.