Help! Resolution field is wreaking havoc

[Teale McCleaf]

Hi Jira Community - 

I'm not sure what is causing this issue.

I have the Resolution field on the field configuration screen and just migrated the teams entire workload to this new company-manage project over the weekend. 

Because the field wasn't appearing when the issue is transitioned through the workflow, I set a default value but apparently that didn't get set with the transfer of the issues.  I've since removed the default value and used a procedure found here to reset some of the issues so that the Resolution field doesn't appear on the screen any longer with the default value but now the field doesn't appear at all when issues are set to a status that equates with Done. 

It was appearing dynamically previously and only stopped appearing when I applied a different screen configuration to the Epic issue type.  The screen configuration was unchanged for all other existing issue types.

Here are images of the settings.

What can I do to resolve this?

Thanks in advance for any help you can offer!

[Nic Brough -Adaptavist- · Accepted solution]

Take the resolution field off the screen, it should only ever go on transition screens.

You set the resolution during the transition to closed, either by setting it during the transition screen, or by having it set by a post function (some boards let you set a simple tick box which does this for you)

[Teale McCleaf]

Hi Nic - 

You're correct.

Alternatively, if you add the Resolution field to the screen and don't associate the transition with a screen, the system doesn't force the field to be populated during those transitions and the field only appears when the issue is set to a status that equates with Done. Works beautifully.  

[Nic Brough -Adaptavist-]

I'm  sorry, but  that does not work.

If resolution is put on a screen, it has to be filled when the screen is used.

[Teale McCleaf]

I'm sure you're right because I've only been doing this for a little over a year and am still learning but it is working in my instance. 

Thanks!