Hi, I know how to set default value, but it is possible only after the field was already created with None value. I would like that from creation it will get a default value (for example 0). Is it possible?
The reason is that I'm adding a new field and after creation I need to run a bulk operation on thousands of records to set the value.
Thanks.
FYI - Atlassian opened a new Feature Request and if this issue bothers you too, please vote for it HERE
Dear community, I've reached out to Atlassian and indeed they don't have a solution for this beside the work around of bulk operation. They did opened a new request for this HERE , so if this issue bothers you too please vote for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If a add a default value of a custom field (f ex "0") and apply the field to the create screen of the issuetype then the custom field value appears with "0" when I create the ticket. Even if it isn't on the create screen and only on the view/edit screen it will appear with value "0" after issue creation.
If you want to avoid the custom field to not be empty at any point during the life cycle of the issue, you need to make it required in the field configuration.
Br
Lisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lisa Forstberg thanks for your answer, I have no problem with new tickets cause they will be created with the default value. but what about existing items they will get the field with the None value and only bulk operation will update them. And that is my question - can we avoid the bulk operation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
aha now I got you. No sorry, adding a default value after the fact that a lot of issues has been created with a "none" value, will not have a retroactive effect.
You will have to bulk update your existing issues. The last updated date will be affected but you can do the bulk update without notifying users at least...
best of luck!
/L
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lisa Forstberg thanks Lisa, I think it's something Atlassian need to consider to develop, when you create the new field , set the default value from the beginning and then the new field in existing items will be created with the default.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.