How to aggregate Time effort from Task/Story/Bug into Epic?

[Aleksandar Ilijevski]

Hello,

I got a request from one of the users if I can aggregate Time effort from Task/Story/Bug into Epic. I have tried several solutions like:

https://www.scriptrunnerhq.com/help/example-scripts/sum-custom-field-related-epic-issues-cloud

or 

https://www.youtube.com/watch?v=CX5haGHkf0c (I have adjusted it slightly to the DC variant of Jira automation)

but non of these solutions work.
Do you see any impedence that this will not work or do you have some advice how to achieve this?

The time aggregation is working from subtasks to Task/Story/Bug, but above that level I can't make it work.

Thanks in advance!

[Jack Brickey]

Hi @Aleksandar Ilijevski , It is quite likely that you are referencing an unsupported automation feature in DC. By chance, are you referencing a custom field within a lookup issues function? Unless something is changed, I know that that is still on supported in DC. At the same time, it is odd that it is working for sub tasks to tasks. It's hard for me to tell from the JSON here.

[Aleksandar Ilijevski]

Hi @Jack Brickey ,

Sure.

Here is the Jira automation export json:

---

{
"rules": [
{
"id": 83,
"clientKey": "com.codebarrel.tenant.global",
"name": "Sum Timetracking from stories/tasks to epics",
"state": "ENABLED",
"canOtherRuleTrigger": false,
"notifyOnError": "FIRSTERROR",
"authorAccountId": "JIRAUSER16205",
"actorAccountId": "JIRAUSER16205",
"created": 1743170712348,
"updated": 1743588620137,
"trigger": {
"id": "276",
"component": "TRIGGER",
"schemaVersion": 2,
"type": "jira.issue.field.changed",
"value": {
"synchronous": false,
"fields": [
{
"value": "timetracking",
"type": "field"
}
],
"actions": []
},
"children": [],
"conditions": [],
"optimisedIds": [],
"newComponent": false
},
"components": [
{
"id": "277",
"component": "CONDITION",
"schemaVersion": 3,
"type": "jira.issue.condition",
"value": {
"selectedField": {
"type": "ID",
"value": "issuetype"
},
"selectedFieldType": "issuetype",
"comparison": "ONE_OF",
"compareValue": {
"type": "ID",
"value": "[\"10100\",\"10001\",\"10302\",\"10101\"]",
"multiValue": true
}
},
"children": [],
"conditions": [],
"optimisedIds": [],
"newComponent": false
},
{
"id": "278",
"component": "BRANCH",
"schemaVersion": 1,
"type": "jira.issue.related",
"value": {
"relatedType": "jql",
"jql": "parent= {{issue.parent}}",
"linkTypes": [],
"onlyUpdatedIssues": false,
"processIssuesInBulk": false
},
"children": [
{
"id": "279",
"component": "CONDITION",
"parentId": "278",
"schemaVersion": 1,
"type": "jira.issues.related.condition",
"value": {
"relatedType": "parent",
"linkTypes": [],
"operator": "present",
"relatedJql": "",
"compareJql": "",
"jql": ""
},
"children": [],
"conditions": [],
"optimisedIds": [],
"newComponent": false
},
{
"id": "280",
"component": "ACTION",
"parentId": "278",
"schemaVersion": 6,
"type": "jira.issue.edit",
"value": {
"operations": [
{
"fieldId": "originalEstimate-timetracking",
"fieldType": "originalEstimate-timetracking",
"type": "SET",
"value": "{{#=}}{{lookupIssues.Original estimate.sum}}/60{{/}}"
},
{
"fieldId": "remainingEstimate-timetracking",
"fieldType": "remainingEstimate-timetracking",
"type": "SET",
"value": "{{#=}}{{lookupIssues.Remaining estimate.sum}}/60{{/}}"
}
],
"advancedFields": "",
"sendNotifications": false,
"useLegacyRendering": false
},
"children": [],
"conditions": [],
"optimisedIds": [],
"newComponent": false
}
],
"conditions": [],
"optimisedIds": [],
"newComponent": false
}
],
"projects": [
{
"projectId": "12500",
"projectTypeKey": "software"
}
],
"labels": [],
"tags": []
}
],
"cloud": false
}

The log:

I assume that there is something above that is only related to the Cloud and I am running Data Center variant of Jira.

Regards,

Alex

[Jack Brickey]

Hi @Aleksandar Ilijevski . Could you share your rule and also the audit logs?