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

Resolution field is not being set

Pankaj Mehta

My transitions are set properly, where "Update Issue Field" post-function sets the resolution to Done once the issue is transitioned to the Done status. The "Resolved" field is also populated with the resolved date. But the "Resolution" field is still empty. Please advise on how i can populate the resolution field moving forward and for historical issues.

Thanks

Pankaj

Accepted answers

Pankaj Mehta

Thank you all for all the ideas and support. Atlassian support helped figure this out. The Field Configurations had the Resolution field as Hidden and hence was not updating. Thank you.

All comments

John Funk

Hi Pankaj,

You should be able to add a post function on the transition to Done that sets the Resolution field to Done.

Pankaj Mehta

That transition is already set and maybe thats why i see the "Resolved" field with a date. But the "Reolution" field is still empty.

John Funk

Maybe check the History of the issue to see if something is coming behind and clearing it out? Otherwise, not sure why there's no value there.

Pankaj Mehta

Hi John,

Thanks for the quick responses. Here is what i see in the History

I don't see anything that is clearing the Resolution field. If I run a JQL with "Resolution WAS Done", I see the issue in the search result, but "Resolution = Done" does not give any results.

Also, how can i update the "Resolution" field using a bulk update and set it to "Done"?

Please help.

Thanks

Pankaj Mehta

Thank you all for all the ideas and support. Atlassian support helped figure this out. The Field Configurations had the Resolution field as Hidden and hence was not updating. Thank you.

John Funk

Great - thanks for the update!

George Mihailoff

For the historical issues, you can try our free addon, because we deal with things like time in status, throughput and other Kanban metrics we already know what resolution dates to suggest. There is a special tool called "resolution checker" that allows you to fix this.

I guess, your post function is configured based on the recommendation here -- https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html?

desarrollo

Thanks for the info!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software