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!
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.
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.
I agree it is hard to support. That is why I don't recommend doing it for fun. Heavy customization comes at a cost!
But yeah, it is good to have a way though. In some tools (avoiding names for obvious reasons), it costs a lot more time and dollars
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG