All our projects are created using a standardised project template with a common set of workflows and fields. However, some projects do not require most of these fields.
In our on-premises environment, we used the CreateIssueDetails URL with query parameters to pre-populate fields. This allowed us to provide a customised creation form containing only the fields relevant to each application. However, in Jira Cloud, the CreateIssueDetails screen displays all fields configured for the Create screen instead of showing only the required fields and preset values.
We have found an alternative using space forms, which allows us to create customised forms by dragging and dropping the required fields. However, space forms do not currently support preset default values, making the process less streamlined for our users.
We understand that URL-based field pre-population and post-creation automation may serve as alternative solutions. However, we do not consider these to be sustainable or user-friendly approaches in the long term.
Could the Atlassian team please provide an update on whether support for preset default values in space forms is planned and, if so, when it is expected to become available?
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.