Default Values - Text not clearing with new issue type.

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.

Thanks.

1 answer

Hi Chris,

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:

  • If you DO NOT change default text in a field and switch issue type:
    • 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
  • If you DO change default text in a field and switch issue type:
    • Field value is preserved if there is no default value for the new issue type (so what you enter is still there)
    • Field values is replaced with new default value if the destination issue type has it defined

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.

Cheers,
Gebsun

hmm.. this is not the behaviour I am seeing. I'll have to dig into a little bit more and see if maybe I configured something weird.

Let us know the details if you can reproduce some other behaviour. We are keen to inspect that and fix potential bugs.

Ok, the behaviour seems to be consistent as 'wrong' changing issue types leaves the default text in the field. It does not revert to blank even if no text has changed. What additional information do you need from me?

Does it happen when destination issue type has no defaults? Are you sure that destination issue type has no the same defaults? Please double check your configuration. Thanks, Gebsun

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

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot