nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Need to Sum Timetracking on Parent Issue

Sanjivani Wayal

Hi,

Story is linked to BPT or Interface with linked name "Connection Child" ( This is project need) i am trying to Sum the time tracking but it says no action performed Automation is below in scheduled i have given issue key of Story, Even if i remove the If:Linked issues condition it doesnt work, Can anyone help what should be the calculation as I think lookup wont work in this case

Calculation for updating time tracking is

{
"fields": {
"timetracking": {
"originalEstimate" : "{{lookupIssues.Original Estimate.sum .divide(60)}}",
"remainingEstimate" : "{{lookupIssues.Remaining Estimate.sum .divide(60)}}"
}
}
}

I Even tried below -

{
"fields": {
"timetracking": {
"originalEstimate": "{{issue.timetracking.Original Estimate.sum .divide(60)}}",
"remainingEstimate": "{{issue.timetracking.Remaining Estimate.sum .divide(60)}}"
}
}
}

Accepted answers

All comments

Trudy P Claspill

Hello @Sanjivani Wayal

Whenever asking for help with an Automation that is running but not providing the expected results it is helpful to us if you also provide the details available in the Audit Log for the execution of the rule.

Using the For Each Parent branch will try to look for the issue designated as the parent. That is the issue identified in the Parent field. This is not the appropriate option for issues that are connected through Issue Linking. In your case the branch is trying to find the parent Epic for the Story, and then find issues linked to the Epic.

To ensure we understand your scenario correctly can you provide a screen image of the issue where you want the sum recorded, including in that image the portion of the screen that shows the issue's relationship to the linked issue you want to sum up?

Sanjivani Wayal

@Trudy P Claspill

LOGS are below -
Log
SmartTimetrackingBean{source=TimetrackingBean{originalEstimate='null', remainingEstimate='null', timeSpent='null', originalEstimateSeconds=0, remainingEstimateSeconds=0, timeSpentSeconds=0}} TimetrackingBean{originalEstimate='null', remainingEstimate='null', timeSpent='null', originalEstimateSeconds=0, remainingEstimateSeconds=0, timeSpentSeconds=0}

Changed the automation as below -

Sanjivani Wayal

Also below is field of Main issue where i need to sum the values from Stories

Below is the link type used -

And this is value in Story -

Trudy P Claspill

Hello @Sanjivani Wayal

When I asked about the details of the audit log I meant all the details for a full execution of the the rule. There should've been more entries in the log for the one execution than just the entry for the Log action.

When you put a branch into your rule, the effect is that the focus shifts from the issue that triggered the rule to the issue selected by the branch. The actions and conditions you have within the branch are going to be applied to the issues found by the branch.

With the latest version of your rule, your For Each branch is shifting the focus to the linked issues, printing information from the linked issues, and then trying to edit the linked issues, because the Log and Edit actions are within the branch.

Instead, use the Lookup Issues action to execute a JQL statement to find the linked issues. That will give you an object that contains the linked issues. This function gives you the linked issue of a particular link type related to a specified issue.

https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#linkedIssues--

issue in ({{triggerIssue.key}},"Connection child")

You'll want to confirm that you got some issues back from that action using an Advanced Compare to check the size of the list.

{{lookupIssues.size}}
greater than
0

You can then get the sum of values of a numeric field in that collection of issues using the smart value

Time duration values are typically stored in seconds. You may have to so take that into consideration when using that sum to set the value of the Story.

I recommend that you try the rule first by using just Log actions to print the information you want to use into the rule execution audit log, and then add the Edit action after you confirm you are getting the correct values.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud