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

"Resolution" default selection in the pick list global only?

Dennis Gross_f9jmok

I know, it has been asked in different ways before, but I don´t get it or can´t accept it.

Is it right, that the default value in the resolution pick list can only be set generally, for our complete Jira?

No way to change it project- or screenwise?

I got the request on my table to change the default value to "resolved" (which is set on "unresolved" in general) in one screen of one specific project. To set the resolution per transition property was not accepted by the user, because the choice should be kept as before, only with another default. Almost going crazy about this detail. Appreciate your advice!

Accepted answers

Joe Pitt

I caution you about having a default for ANYTHING. From much experience with JIRA and other tools people don't change the default so you can't really run reports that show any kind of trends for the value of defaulted fields. You can use the workflow. I suggest using the jira.field.resolution.include workflow property to limit the resolutions available in a particular transition. See the link below.

https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

All comments

Jobin Kuruvilla [Adaptavist]

Unfortunately, yes. You will need to add some javascript hack to change the default value, if it is a deal breaker!

Dennis Gross_f9jmok

Thanks Jobin for your superfast reply which unsurprisingly doesn´t totally satisfy me wink . But so i understood right. Smells like the need for a coder taskforce on board...

Joe Pitt

https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

Jobin Kuruvilla [Adaptavist]

Sorry to break the bad news! But one reason I like JIRA is the possibility of workarounds, be it via plugins or hacks. As long as you are not doing it for the fun of it wink

Joe Pitt

It's fun until you have to refit a hack that isn't documented into a new release.

MattS

Yes, we've found that JavaScipt hacks are pretty hard to support long-term. Joe's answer about how to restrict the available resolutions is good but doesn't allow you to set a different default per workflow. Perhaps a Behaviours Initializer script might let you do that better.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration