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; } } }

Resolved date not allocated to transitioned calls - Automation for Jira

leandi.mollentze@hensoldt.net

Hi everyone!

We are currently using automation for jira to transition issues that have been in a waiting for customer state for 14 days to resolved. This works perfectly except that a resolution date is not assigned to the issue.

This is skewing our reporting data.

When we do this manually (transition the issues ourselves) the date is assigned. It is only when it is handled through the automation that no date is assigned.

Why is this and how can we resolve it?

Automation Rule.JPG

Accepted answers

All comments

Jack Brickey

If you are setting the Resolution then there should be a resolution date. Check to ensure the resolution is in fact being set.

koelofse

Nope - no date is being set. See the extract below - resolution is set. No date.

Resolution Date.JPG

Jack Brickey

Odd for sure. I assume if you manually transition the date is set?

leandi.mollentze@hensoldt.net

That is correct which is what I am currently having to do to rectify the skewed data. Problem is we cannot keep using this automation if it is going to keep doing this in future.

Brett Palmer_d49fdp

You need to have the transition post-function set the resolution then that transition will update the resolution date field.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server