Details
-
Suggestion
-
Resolution: Unresolved
-
8
-
12
-
Description
Update added 30 January 2024:
Issue Summary
Required Field not placed on any screen still prevents an issue to be created.
Steps to Reproduce
- Associate a field configuration to a project.
- Put any field of the associated field configuration as required.
- Do not place this field on the screen associated to an issue type
- Try to create an issue.
Expected Results
Issue created successfully.
Actual Results
Even without being shown on the screen, an error message is shown saying that the field is required:
Related documentation
Troubleshooting required-field errors
Description before 30 January 2024:
Hi everyone,
Thanks for your feedback on this problem. We appreciate the time that you took to help us be better.
Though not ideal, this behaviour in-product today is not a bug. Proposed behaviour of Screens here are a feature request and have to be prioritised against other requests.
The layout and fields that appear on screens must be defined in the Screen configuration. This also includes any required fields, to learn more about defining your screen (See Defining a Screen).
We're using bugs to track any issues that prevent our features from being used as intended.
But we also understand and appreciate the expectations you have of our product so we have converted this to a feature suggestion instead.
Please watch this Jira issue for future updates as we continue to work on improving our product.
Regards,
Andrew Trieu
Atlassian
Problem Definition
As a user, I modify my field configuration and turn a 'field' into a Required Field. I expect this required field to be visible on my Issue Create and View screens as I will not be able to proceed with issue creation without populating this field.
Currently required fields need to be defined in the Screen view otherwise they will not be visible. This means I will not be able to proceed with Issue Create unless I define that field in the Screen View.
Suggested Solution
Automatically may required fields visible in the Issue Create screen.
Steps to reproduce
Modify field configuration and make Affects Version a required fieldCreate new Scrum Sample boardClick on + to create a new epic
Excepted Result
Required fields show up
Actual Result
Affects Version is missing
This does not only apply to the Affects Version field, but any required field.
Workaround
Add field to appropriate screen (See Defining a Screen)
Attachments
Issue Links
- is duplicated by
-
JRACLOUD-76273 Required Field not placed on any screen is preventing an issue to be created
- Closed
- is related to
-
JSWCLOUD-9339 Create Epic dialog does not remember which fields should be displayed
- Closed
-
JRASERVER-59074 Required fields does not show up when creating a new epic from plan view
- Gathering Impact
- relates to
-
JSWCLOUD-22862 The “Show fields” button in the Create Epic dialog allows to configure which fields are to be displayed, however, these settings are not persistent and needs to be selected each time an epic is created
- Gathering Impact