Automation outputs 0

Dennis Butijn July 2, 2024

 

 

Hi there, I had an automation rule running for a while but after some time it broke. I think it had to do with me creating a 2nd project with the same fields for the same issue type.

In my example I created 3 custom fields under a user story "Art tracked hours - Item", "Design tracked hours - Item", and "Tech tracked hours - Item". In the sub-task field, I also added 3 custom fields "Art tracked hours - Sub-task", "Design tracked hours - Sub-task" and "Tech tracked hours - Sub-task". I got 3 similar automation processes running, one for art, design and tech. Whenever for example the art tracked hours - sub-task is updated, it should sum up all the art tracked hours from all sub-tasks in the story, and place that value in Art tracked hours - item of the user story.

This all worked fine, but it now outputs 0 for some reason.

I'm using the code {{issue.subtasks.map(fieldValue("Design tracked hours - Sub-task")).sum}}.

I'm aware of the field having 2 "m" at the end. Due to the other project it found 2 of these fields so I had to rename this one.

I did check and they are the same field type (both numeric fields).

 

image_2024-06-14_112915334.png

 

image_2024-06-14_113539231.png

 

image_2024-06-14_113553804.png

1 answer

0 votes
Rudy Holtkamp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 2, 2024

Hi @Dennis Butijn ,

Could you provide a screenshot of the rule details and the details of the edit issue action?

Dennis Butijn July 5, 2024

I managed to solve the issue by renaming the sub-task field to something shorter. I called it "Design Hours" and it now works for some reason.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events