-
Bug
-
Resolution: Fixed
-
Medium
-
5
-
Severity 3 - Minor
-
Issue Summary
Using the new create issue experience doesn't apply the default value for custom fields.
Steps to Reproduce
- create a custom field using an app
- define the custom field value to be the defaultValue for a projects
- create a new issue with such custom field
Expected Results
The configured default value is selected by default.
Actual Results
The configured default value is not selected by default and the users have to manually select it.
Known impact on apps
This is impacting the Tempo Timesheets - Time Tracking & Reports app.
For this app, when setting a Default Account for a Jira Project, the selected Account will not be used in the new create issue modal.
Workaround
Since this only occurs when using the new create issue experience (https://community.atlassian.com/t5/Jira-articles/Announcement-New-Issue-Create-modal-will-be-available-to-all/ba-p/1874003), the workaround is to switch back to the legacy Issue Create modal by going to Personal Jira Settings -> Jira Labs -> New Global Issue Create Experience -> Switch to the old Experience.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-78274] Using the new create issue experience doesn't apply the default value for custom fields
Hi everyone,
Thanks for your patience on this bug, we have released a fix and it should be available for everyone. If you are still experiencing any issues related to this, please comment here to let us know the specific case.
Thanks,
Raghav
Software Developer, Atlassian
Hi ccurti,
We have fixed this issue and today the fix has been deployed for all the customers. Can we verify this from the affected customers?
Thank you,
Raghav
Software Developer, Atlassian
This is causing issues for my company also. We are trying to implement the default account at project level to ensure customer billing is accurate. Please implement a fix as soon as possible.
Our business uses Tempo timesheets with the Account field that used to be automatically set by a default value. However the new Issue Creation rollout has broken this workflow.
It is absolutely essential that the account field has a default value as this is throwing out our client billing as well as our reporting to view profitability by project.
Please raise the priority of this request and get this fixed urgently.
We use Tempo timesheets with the Account field that was set by a default value. The New Issue Creation Experience has broken this workflow.
Everyone at our company has had to switch to the old experience to keep Accounts consistent for the accounting department. This workaround will only work for a couple months. It is absolutely necessary we ensure the account field is populated.
Please raise the priority of this item and schedule a fix to be implemented.
Same here!
We are using Tempo timesheets and we have the `Account` field that has a default value and is also required.
This prevents us from any creating new issues.
It is imperative that we ensure the account field is populated for all issues because this is used when we calculate our client billable work.
Hi, we have the same in our instance. That's very uncomfortable for our employees.
I have the same problem.
We are using Tempo timesheets and we have the `Account` field that has a default value and is also required.
This prevents us from any creating new issues.
It is imperative that we ensure the account field is populated for all issues because this is used when we calculate our client billable work.