So basically, we are using the Default Values plugin for the default issue type. Whenever the issue type is changed (i.e. from Bug to Feature) the Default text remains in place. I believe I am pretty much stuck with this behaviour, since it seems to be a JIRA thing, meaning anytime I enter text and change issue type, matching fileds will still have the text I entered.
Just looking for a sanity check, or maybe if someone knows a trick.
We try to make this behaviour as natural as possible so when you switch issue types and Issue Create page is refreshed Default Values works following way:
Actually only the last bullet is "not natural" but in this case we would need to ask user directly what to do.
Please let us know if you think we should improve the above algorithm or you think you found a bug.
I have just tested it again and it works exactly as planned, so ff you DO NOT change default text in a field and switch issue type then: * Field is erased if there is no default value for the new issue type * New default value is put if the destination issue type has it defined There must be something special in your case. If you can provide more details then we can try to investigate the problem more closely. Feel free to contact us directly through email: support (at) gebsun (dot) com
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs