Ok, that means they're working.
Thing about a default value is that you only want to default it on issue creation.
During an issue edit, there is an existing setting for a field, even if that setting is "empty". The users have deliberately chosen that value, and you do not want to have a default override it. So default settings only apply on "create issue"
You don't really want to do it - that's why Jira doesn't do it.
If your users leave a field blank at creation time, then why would you encourage them to accidentally set it during an edit? It's blank for a reason.
If you do this, you'll find a LOT of your issues suddenly have defaults splattered all over them when you REALLY don't want it.
Hi all! Lauren here from the Enterprise Cloud marketing team. I have some exciting Cloud updates from #AtlassianSummit that I wanted to share. We want everyone in your organization to be ab...
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