-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.15.0, 8.20.0
-
8.15
-
1
-
Severity 3 - Minor
-
Issue Summary
If we have two or more sub-task issue types in a project if you create a custom type sub-task from a plan that has some mandatory field on the create screen. While doing review changes, set mandatory field pop-up does not allow to choose issue-type as a subtask.
Steps to Reproduce
- Create a custom Sub-task type test-subTask. (make sure you have two issue-types of subtask in the project)
- Set any field mandatory in that project field scheme.
- Create a plan from the project
- Try to create a test-subTask issue from the plan.
- Click on "Review changes"
- Click save changes, a set mandatory field box will pop-up
- Verify the drop-down for issue type. It will not have any sub-task issue-type.
Expected Results
The "Set required fields" screen should have issue-type selected as test-subTask
Actual Results
It doesn’t show any sub-task issue type
Workaround
Do not create an issue from the plan. Create impacted sub-tasks from Jira create screen/issue details view.
- is related to
-
JSWSERVER-26125 The "Set Required Field" screen does not take into account mandatory fields from ScriptRunner behaviors
- Short Term Backlog
- links to