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

[Manoj 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 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.

[kamal_a_nayan]

[Trudy 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 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.

[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?

[Trudy Claspill]

To me, a field which cannot be set via automation rule should not be available for a selection.

This would require extensive changes to the Automation Rules functionality to try to

1. determine which issue type in which project was being edited

2. look at the Field Configuration Scheme for the project and the Field Configuration for the specific issue type to see if the field is hidden.

3. Look at the Issue Type Screen Scheme for the project, find the Screen Scheme for the specified issue type, and then find the Screen associated with the Edit operation to see what fields are available.

4. Look at the Workflow for the issue type to see if there are any configuration elements there that would block editing the field.

5. Consider any third party apps that might modify the accessibility of the field...

Feel free to open a suggestion with the Atlassian Team to ask them to consider making that change, though.

Can a default value eg Open be not set by Atlassian like it sets Fixed for that field when an issue is being closed?

Setting a default value for the field when it is not in a done/closed/finished status causes other problems.

Jira has built-in functionality to determine if an issue is Resolved. That functionality says the issue is Unresolved if the Resolution field contains no value. If the Resolution field contains ANY value then the issue is considered Resolved. So adding a Resolution value of "Open" and having the field set at all times would result in Jira considering the issue Resolved.

[kamal_a_nayan]

Thanks Trudy for the explanation

[Trudy Claspill]

You're welcome.