Hi there,
Using automation, I need to set the Resolution field back to Unresolved. The problem is that 'Unresolved' is not listed in the drop-down when trying to do it through the Edit Issue selection. So I have to use JSON. I've tried a few different things and nothing has worked so far. This is what I've tried so far:
{
"fields": {
"resolution": { "id": null }
}
}
{
"fields": {
"resolution": null
}
}
{
"fields": {
"resolution": ["Unresolved"]
}
}
Hi @Chris Robbins , welcome on the community. I'd suggest you to use the workflow's postfunction to set or clear the resolution (as @Alex Koxaras _Relational_ suggests), but if your use case requires to use the Automation, you need to do it using following setup. Let me know if you need more help :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does not work:
(Could not find valid 'id' or 'name' in resolution object. (resolution))
Now the post function is not an option if we have no access to edit it (by rule of company)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a similar situation. Linked issue inherits Status & Resolution from Linked Story
and it is fails with error
Our workflow does have
Clear Resolution post-functions on Open and In Progress . And Resolution field screen on Closed Transition with a Validator of Resolution field being required.
Any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Get rid of the validator on the close transition, you do not need it.
Then reverse the two actions for "edit" and "transition" - you need to set the resolution before you transistion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- You are the best. I retained validator to skip it for Test Issue type and your solution of swapping edit and transition worked. Resolution has to be before Transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh, Does it work for you changing resolution to null? I have tried similar solution as exposed but always having same result:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Clearing the resolution field is indeed a puzzling topic in Jira:
When I create automations which are triggered manually on a preselected issue, I found that this JSON snippet in the action "Edit Issue" works fine:
{
"fields": {
"Resolution": null
}
}
On the other hand, when I create scheduled automations, which run on a JQL-filtered set of issues, that very same approach to clear the resolution field does not work and thows error messages as follows:
"enter Resolution (id or name) in text sting format (resolution)"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This can't work because the REST API, and Automation works the same way that the UI does.
If you put the resolution on an edit screen, you don't get an "unresolved" or "none" option, and the system will default it to a value, so you have no option but to set it to something.
You can't blank out a resolution by editing an issue. You have to do it by transitioning an issue to an open status and using a post-function to clear the resolution, exactly as @Martin Bayer _MoroSystems_ s_r_o__ says.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Chris Robbins and welcome to the community,
I would expect that ""resolution": null" would work. What response are you getting?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Chris Robbins you have to transition the issue and during that transition the resolution can be cleared.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please show an example of how to do this using a Jira automation? - Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.