Details
-
Bug
-
Resolution: Duplicate
-
Low
-
31
-
Severity 3 - Minor
-
Description
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Steps to reproduce:
- Go to General Configuration and set Allow unassigned issues setting to Off. The Assignee field will be automatically set to Required in the Field Configuration.
- Create a new project and make the Project Lead as the Default Assignee
- Go to Project Administration -> Issue Collectors -> Add Issue Collector
- Key in all the required field and click Submit
Current Result:
- The page is refreshed and returns to the same page without any error message shown until the users change the Issue Type
Expected Result:
- The error message should be displayed without changing the Issue Type
Error You cannot create an issue collector for this project, because the following fields are required on the project and those field types cannot be displayed to anonymous users. If the field is changed to be optional or a default value is provided, then an Issue Collector can be created for the project. Not allowed fields: Assignee
Workaround:
- Set Allow unassigned issues setting to On in General Configuration
Attachments
Issue Links
- has a regression in
-
JRACLOUD-75743 Issue collector edition fails silently when "Allow unassigned issues" is turned off
- Closed
- is duplicated by
-
JRACLOUD-43036 Issue Collector cannot be created if Assignee is forced to Default Assignee
- Closed
-
JRACLOUD-65284 Issue collector can't be created due to certain field without any error thrown properly
- Closed
- is related to
-
JRASERVER-43028 Issue Collector Error Message is not shown without changing the Issue Type
- Gathering Impact