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

Not able to set resolution value to complete in Jira automation

kamal.a.nayan

Hi,

I have set up an automation rule to change the Resolution field value to Complete instead of Fixed (seems to be Jira default) however I get an error when it is being executed. What is wrong in my rule setting. What I am noticing is that Complete is shown under Edit issue but Then: Edit IssueFields on the left is showing Resolution only ; not the value (Complete) which I want. If that is reason, what I need to do to have this value appear under Then. Probably a trivial thing but I am not able to find. Thanks

Accepted answers

All comments

Trudy P Claspill

Hello @kamal.a.nayan

Please provide a screen image showing the error you are getting.

The step on the left is showing only the name of the field being edited as part of the Edit Issue action. It will not show the value to which that field is being set. The value will be shown only on the right where the details of the Edit Issue action are shown. It is not possible to make the value also show in the steps diagram on the left.

Manoj Kumar Gangwar

Hi @kamal.a.nayan you can set the resolution using the workflow post function instead of automation.

Also, please share the automation audit logs screenshot to check the error.

kamal.a.nayan

Manoj,

I cannot modify the workflow post function as it is used by other teams as well who don't need this functionality.

Trudy P Claspill

Hello @kamal.a.nayan

You will not be able to set the Resolution field during an Edit Issue action if the Resolution field is not present on the Edit Issue screen that you see when editing the issue manually.

And the Resolution field should never be on any Create or Edit Issue screens. When the field is available in those screens it requires you to select a value, and you don't want the field be be required except when an issue is being transitioned to a closed/done status.

As mentioned by @Manoj Kumar Gangwar , if you want to set the field to Complete instead of Fixed by default, then you should instead change the workflow(s) associated with the issue types and projects where you want to apply that change. Typically the Resolution field is set as a Post Function in the transitions to closed/done statuses.

Screenshot 2025-01-27 at 2.08.54 PM.png

kamal.a.nayan

Hi Trudy,

Thanks for advising that a field which is not available in the Edit Issue screen cannot be used for automation. However, I am wondering then why Atlassian let a user select that field. To me, a field which cannot be set via automation rule should not be available for a selection.

Further, you mentioned that Resolution field should not be in the Create/Edit issue screen as a user would have to enter a value each time a issue is created, Can a default value eg Open be not set by Atlassian like it sets Fixed for that field when an issue is being closed?

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-cloud