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

Why can't I add the Resolution post to a status

Beth Schwartz_qglyii

In Jira we currently have 2 statuses that when selected the resolved data is timestamped and they are considered resolved. That was done by going to the transition to that status and adding the post that "the resolution will be set to done"

When we try to do the same with a another status, there is not an option to add same post "the resolution of this issue will be set to Ready for Deployment"

Why is the resolution post function not available?

Accepted answers

John Funk

Hi Beth - Welcome to the Atlassian Community!

Select the very last option for the Post Functions = Update Issue Field.

There you will be able to select the Resolution field and the value to put in it.

But sure to save that and then publish your workflow.

All comments

John Funk

Hi Beth - Welcome to the Atlassian Community!

Select the very last option for the Post Functions = Update Issue Field.

There you will be able to select the Resolution field and the value to put in it.

But sure to save that and then publish your workflow.

Nic Brough -Adaptavist-

Be warned, setting a resolution means the issue needs no more action from anyone. It doesn't matter what the resolution is called, your "ready for deployment" means "no-one needs to do anything with the issue". So your deployment team is going to struggle to report on it. Things like "assigned to me" only display unresolved issues.

Joseph Chung Yin

@Beth Schwartz -

Welcome to the community. To supplement what @Nic Brough -Adaptavist- and @John Funk provided, it is important to not to set resolution field value unless the status associated to the issue is considered to be terminal (i.e. CLOSED, DONE, or CANCELLED).

Resolution field is a critical field in the system. This is why when issue moves back from a "terminal" status, one will need to ensure the resolution field is set back to None - Cleared (using the Update Issue Field post function call).

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Beth Schwartz_qglyii

I want to confirm a my need and/ OR understand if something changed.

I am not trying to use the Resolution screen or field.

I only want to make sure the resolution date is applied on the status I want it applied to

So that I get the following action (but different status)

With the resolution date

I currently have this working on 2 statuses that in or org are defined as a done state and have a 3rd I want to also have in a done state, but Jira won't let me do it like I did the others (which was by adding the "Add Post Function to Transaction" and that was the function I was able to assign to the others "the resolve post function not available as an option?

Joseph Chung Yin

@Beth Schwartz -

Sorry for my late response to your update. For your 3rd status that you want to add, all you need to do is to setup transition into the status in your WF and set the Resolution field with a resolution value.

In Jira/JSM, when an issue's resolution field is populated, it will also automatically apply the resolution date. This is a default behavior.

Best, Joseph

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management