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

Set Resolution in an Automation

Greg Tucker

We have an integration that is changing the status of an Incident to Completed, but isn't setting the Resolution field. Resolution field is normally chosen in the Resolve Issue Screen. Unfortunately, not having a working Resolution is breaking some workflow, such as appearing in Queues that it shouldn't, and SLAs not ending correctly.

I created an Automation (new style) to set it, but it returns an error:

Screenshot 2020-11-16 212654.png

Here are details of the Automation. Any idea why I cannot set the field? I am guessing it's a permission issue with the Automation for Jira service (account?) but cannot find where it's defined.

Screenshot 2020-11-16 213300.png

Accepted answers

Liam Green

Hi Greg

Could you change your rule so that it changes the resolution when the issue transitions rather than after? It may be that automation is unable to set the resolution once resolved.

You should also check you don't have another field called 'resolution' as it may be looking to amend the wrong one.

All comments

Liam Green

Hi Greg

Could you change your rule so that it changes the resolution when the issue transitions rather than after? It may be that automation is unable to set the resolution once resolved.

You should also check you don't have another field called 'resolution' as it may be looking to amend the wrong one.

Dirk Ronsmans

A 2nd resolution field has my vote.

The system field you cannot even restrict so I wouldn't even know how to block that. Even when you don't put it on the screen you have it

In your edit issue component, can you check that the field you are setting is the "Resolution (System)" field?

Greg Tucker

Thanks for the reply. I don't see a custom field named Resolution. Also I added a choice to the system Resolution field and see that choice in the Automation, so I think I have the correct field. I will test setting it on a transition. I was hoping to clean up the test tickets, but I can just delete them because they are appearing in Queues they aren't supposed to.

Greg Tucker

I have modified the automation to trigger on update of Status. But the automation is not firing. I tried it initially with drag and drop conditions, but there was no option for Resolution is empty (only an option for Unresolved) but it didn't fire. Should I try status in (Completed, Closed) instead of fieldChange?

Screenshot 2020-11-18 091446.png

Greg Tucker

I tried a couple variations like this but I still cannot get the rule to fire.

Screenshot 2020-11-18 094110.png

Nic Thiele

I (Jira Data Centre) have been unable to clear the resolution field with automation. I just set a post function on the workflow transition instead.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management