Default value of a custom field is not selected

I can not explain following behavior.

We are using a plugin for importing and updating issue from a provider. There is a required custom field that is not populated while creating the issue (we need to check the plugin- but that is another question) .

So here is the question. I have now an issue where I have an empty field (Severity) which by field configuration is required and also has a default value (Normal). If I edit the issue there is immediately a value displayed in that field (Blocker). Can someone explain why 'Blocker' appears in that field and not the default value 'Normal'?



2 answers

You don't have any scripts attached to that field (e.g. behaviours, JS)?

No I don't. One more thing I just found out. Blocker is obviosly picked because it's the first of the options. But still the question remains why the default is not selected.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Apr 17, 2018 in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

763 views 2 19
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