Issue Resolution options change in new tabs

[Joshua Procious]

We have a Jira Software Data Center v8.13.13 running in an Ec2 instance on AWS. We run a fair amount of custom scripting through Scriptrunner and Elements Connect add-ons. Recently, we noticed that on workflow transitions that have a screen, if the workflow button is opened in a new tab (right click on the work flow button > open in new tab), the resolution list is not constrained to what it should be for the project/status. If you just click on the workflow transition button and let it pop up the transition screen on the same tab in the browser, the list IS constrained to what it should be.

Logs do not indicate any errors when this process takes place. 

Has anyone seen this before or have any ideas?

[Tim Perrault]

Hi @Joshua Procious 

Are you using a Behaviour to limit the resolutions?

Thanks,

Tim

[Joshua Procious]

Hey Tim,

No, we are just using the native Issues Resolution Schemes in Jira.

Originally, I believe it was this app that's now bundled?

https://community.atlassian.com/t5/Jira-Software-questions/Issue-Resolution-options-change-in-new-tabs/qaq-p/1929198#M182811

Thank you,
Josh

[Tim Perrault]

Hey Josh,

Which app is that? The link you posted just points here :)

Thanks,

Tim

[Joshua Procious]

Hello Tim,

My copy and paste was everywhere. Thanks for that catch. :)

The app here: 

https://brokenbuild.atlassian.net/wiki/spaces/ADDONS/pages/50462737/Issue+Type+Resolutions

Cheers,

Josh

[Tim Perrault]

Interesting. I'll take a look at the documentation, but I'm going to guess this is a bug in the application. The directions look very simple and from what you describe you have it setup properly.

We limit resolutions on projects too because at one point the users ruled all and every resolution they wanted they got... Anyways we use a scriptrunner behaviour to get this done.

[Joshua Procious]

Hello Tim, 

Thank you for the feeback. After scouring logs and add-on information/settings it does appear to be an issue with the application. 

I will bring up the idea of using behaviours to solve this until we are able to grab the next version of Jira.

Cheers,

Josh