How can I clear the Resolution field in Jira Automation?

[Łukasz Wójcik]

Use case: Issue was set as Done but the it was recognized some work still needs to be done. I know I can set it with post function in my workflow. But then I would need to create transitions from Done to every other step and I would like to avoid that. I'd like to use automation here but I have problems. The only action which is somehow related seems to be "Edit Issue fields". But then I can only set the Resolution to some value. There's no option to clear previously set value. How to achieve that? 

[andreas · Accepted solution]

Hi Seba,

So we don't support clearing the resolution field with our 'Edit issue' action currently, mainly because Jira only supports clearing the resolution field through a workflow post-function: https://codebarrel.atlassian.net/browse/AUT-441

The edit API simply doesn't let you clear the resolution field.

Atlassian have also published  more info on this: https://confluence.atlassian.com/jirakb/howto-bulk-clear-resolution-635896313.html

So I'm afraid for now the only option would be to add a transition in your Jira workflow with a post-function to clear the resolution field.  Then you could trigger this transition with an Automation rule (or any other way). 

Hope that helps.

Cheers,
Andreas

[Łukasz Wójcik]

Yeap, I know these steps and what I really wanted to avoid is 
"Repeat steps 2 and 3 for each status for which the Resolution field will need to be cleared."

But your answer is clear, thank you very much.

[rajdeep_hazarika]

Hi @Łukasz Wójcik @andreas  ,

Would you be able to guide me how you achieved to trigger the "Transition" . The on;y option that i can see is the actual Transition to a Status .

Many thanks.

Cheers,

Raj

[Łukasz Wójcik]

Helo Raj!

I meant Transition to Status. So it seems that Atlassian only allows you to manipulate the Resolution when status is being changed. And you can only do that by workflow. Very inconvenient. 

Considering all the answers in this subject you can see that there is no option to set automation so it allows you to manipulate this field directly. 

Cheers,

Łukasz

[Yaron Azar]

Can be cleared either on status transition post function - clear field value.

Or, via automation (advanced edit issue fields:

[Efrat Noam]

wow!! great help! it worked!

[Nick Thoman]

This should be also a solution. I had a user accidently close a ticket and our re-open workflow didn't reset the resolution to null. We fixed the workflow but needed to fix the old tickets he closed. Using this advanced edit field fixed the tickets that went through the incorrect workflow.

Thanks Yaron!

[Andrew Renfroe]

This worked great. Thank you!

[Sayan Kaiser]

Hi Yaron,

I am getting the following error :

(Could not find valid 'id' or 'name' in resolution object. (resolution))

[Yaron Azar]

Hi,

If still relevant, send screenshot of the automation rule

[Sayan Kaiser]

[Yaron Azar]

@Sayan Kaiser 

Please note - 

In the EDIT block you selected Resolution field to be updated but with no value.
unselect it and lease only the additional fields to run.

[Yaron Azar]

[Jeremy Jedlicka]

@Yaron Azar

I get the same error as @Sayan Kaiser 

I do not have the Resolution field selected.

[David Harkins]

@Jeremy Jedlicka 

Was you able to get this working?

I am getting the same error :-( 

[Daniele Cerfeda]

@Yaron Azar 

I have tried that as well, and I am receiving the same error, even if I created an automation from scratch, with no field selected

[salvinder.nagarro]

@Daniele Cerfeda @David Harkins @Jeremy Jedlicka

The only difference I see is an additional space required before null.
{
"fields": {
"Resolution": null
}
}

[Mark B Wager]

Yes, Salvinder, I agree. I tried it without the space and it fails.  With the space it works.  Note: I've found this true for other syntax in the Advanced Edit window, too. Be careful with your syntax.

Example:  "Resolution":<SPACE>null     WORKS!

{
    "fields": {  
        "Resolution": null
    }
}

Seems strange that this would work since the API doesn't support it, but heck - IT WORKS! So, I'm just glad we have a workaround. :)

Mark

P.S. I suggest the "Accepted Answer" should be updated to accept Yaron Azar's answer. They provide a very easy and working solution. (Thanks, Yaron!!)

[Daniele Cerfeda]

@salvinder.nagarro @Mark B Wager  Still doesn't work for me:

[Marc Thayer]

@Daniele Cerfeda Did you ever get it working?

[Daniele Cerfeda]

@Marc Thayernope...

[Hamzah Mohamed]

Worked for me. The key was to use just null and not "null" with quotes, and I'm using Cloud. Based on your screenshot it might be that you are looking for an answer to server/DC?

[Michael Wohlgemuth _Wolge_]

@Yaron Azar i love you rn. just saying. thanks for this :D

oh and btw: this did not work for me for 5 of 6 issues i had with a wrong resolution. the ONE it worked on was in a blue category (In Progress) status. the 5 where it did produce an error were in a status of green category (Done). I changed the category of the status to grey (To Do) and then it worked for these 5 issues without ANY other change. Keep that in mind. The status category seems to have effects unknown (to me at least).

[Ana Eva Lopez]

Oh man, this was the best answer, thank you!

BTW, I thought I was experiencing what @Michael Wohlgemuth _Wolge_ but then I noticed that the automation just has a slight delay to clear the fields, which once you think about it, it makes sense.  The automation has to detect that the condition has been met, then it has to go set the field as you want it and then the changes need to be reflected back on the screen.

So ultimately, the solution does work for me.  BTW, I use this automation to clear more than just the Resolution field so it is helpful to just be able to clear everything at once vs adding a post function for each field you want to clear. +1 on Yaron Azar's answer.

[Nic Thiele]

I (Jira Data Centre) couldn't clear the resolution field with automation (advanced or otherwise). Instead, I created a workflow transition from the status back to itself, I called it "Clear Resolution", and then I used a post function on the workflow transition to set the value to "None" and it works neatly.

[Guillaume Outters]

Note that feature requests have been opened at https://jira.atlassian.com/browse/JRACLOUD-75100 and https://jira.atlassian.com/browse/JRASERVER-11444.

[Sebastian Krzewiński]

Hi @Łukasz Wójcik 

Indeed, in Automation for JIRA add-on there is no chance to clear field resolution.

Correct me if I'm wrong but do you want to clear resolution field and leave this issue in Done status? Are you sure that is correct procedure to reopen issues? Best practises (also Atlassian reccomend these) are that resolution field should be set during transition to last status and clear resolution when issue is transition from last status (in your case Done status).

In cases where I have to modify resolutions in bulk (e.g. wrong resolution, issue is not in Done status but resolution is set) I create a "loop tranistion" (e.g. from Done to Done like in your case) and set function to clear resolution. Then I transition this issues using loop.

I know, this is not an automatic solution but, as I mention, in my workflows when user reopen issue status is changed and resolution is cleared.

Regards,

Seba

[Łukasz Wójcik]

Hi Seba,

Correct me if I'm wrong but do you want to clear resolution field and leave this issue in Done status? 

No, in my case issue should go to some other state. Cases which I try to cover is mostly when somebody accidentally moved the item to Done. In our workflow it is possible to go to Done from any of the statuses.
Example case: I've moved the item from Testing to Done then I realized I moved wrong item or moved it too fast but there are still some cases to check or any other scenario which explains the work still need to be done. I am able to move the item back because my workflow allow me to do that. By the resolution is not cleared at this moment. As I said, I know hot to clear it just in Jira but the only solution I see is creating several transitions. I try to avoid that and use Automation here. But Automation seems to lack "Clear field value" option...

[Kelly Arrey]

I'm in the same situation as Lukasz. I have multiple workflows which use "From All Status" transitions.  So in order to clear Resolution when an issue is moved out of the Done status, for example, I have to add a post function to every transition (except one), across all workflows. I can use automation to edit the Resolution, but not to clear it. It seems like a very unfortunate design decision by Atlassian to disallow this. Incidently, we use the JSU Automation Suite plugin to enable clearing the Resolution in a transition post-function.

[Jordan Duggan]

This is really frustrating. In the old UI, I can see and change resolution status, but I can't clear it. In the new UI, I can see the resolution value, but not change it or clear. So when the resolution value is incorrectly set (because a story that was marked done was re-opened), the incorrect value just sits there taunting me. This is a very common occurrence and it's absurd that a value can be changed by automation but not manually. 

[Tim Perrault]

@Jordan DugganCouldn't you just put the resolution field on the edit screen? I mean I wouldn't, but the suggesting of clearing the resolution on transition doesn't seem like a solution for you guys...

[Kelly Arrey]

As I understand it, the Resolution field doesn't work like that. It can only be set during a transition. But that gives me an idea.

On second thought, never mind. My idea was to create a transition to clear the Resolution, and then trigger then transition from the automation. It honestly sounds like more trouble than its worth.