-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the screen used by the "create issue" operation, a screen will pop up so that the user fills the data for the required field.
In this moment, Jira won't remember which subtask issue type the user has previously selected. You can view the following video about this:
Steps to Reproduce
- Access an issue (that is not a subtask) using the New Jira Issue View;
- Be sure you have multiple subtask issue types available;
- Be sure you select a subtask issue type which has a required field in the screen used by the "create issue" operations;
- Try to create a new subtask;
- Select a random subtask issue type;
- Fill the Summary field;
Expected Results
- Jira will open a popup, and the random subtask issue type selected.
Actual Results
- Jira will open a popup with the first subtask issue type available
Workaround(s)
- Although probably not feasible, a workaround would be admins to make the field in the screen used by the "create issue" operation optional.
- duplicates
-
-
- Closed
-
[JRACLOUD-71782] In the New Jira Issue View, when creating an inline subtask which has a field required, Jira won't remember the subtask type
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 3123124 ] | New: JAC Bug Workflow v3 [ 3361353 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Link |
New:
This issue duplicates |
| Support reference count | New: 1 |
| Component/s | New: Issue Creation [ 46596 ] | |
| Component/s | Original: Navigation [ 46540 ] |
| Description |
Original:
h3. Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the screen used by the "create issue" operation, a screen will pop up so that the user fills the data for the required field. In this moment, Jira won't remember which subtask issue type the user has previously selected. You can view the following video about this: [^ h3. Steps to Reproduce * Access an issue (that is not a subtask) using the New Jira Issue View; * Be sure you have multiple subtask issue types available; * Be sure you select a subtask issue type which has a required field in the screen used by the "create issue" operations; * Select a random subtask issue type * Try to create a new subtask, filling the Summary field; h3. Expected Results * Jira will open a popup, and the random subtask issue type selected. h3. Actual Results * Jira will open a popup with the first subtask issue type available h3. Workaround(s) * Although probably not feasible, a workaround would be admins to make the field in the screen used by the "create issue" operation optional. |
New:
h3. Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the screen used by the "create issue" operation, a screen will pop up so that the user fills the data for the required field. In this moment, Jira won't remember which subtask issue type the user has previously selected. You can view the following video about this: [^ h3. Steps to Reproduce * Access an issue (that is not a subtask) using the New Jira Issue View; * Be sure you have multiple subtask issue types available; * Be sure you select a subtask issue type which has a required field in the screen used by the "create issue" operations; * Try to create a new subtask; * Select a random subtask issue type; * Fill the Summary field; h3. Expected Results * Jira will open a popup, and the random subtask issue type selected. h3. Actual Results * Jira will open a popup with the first subtask issue type available h3. Workaround(s) * Although probably not feasible, a workaround would be admins to make the field in the screen used by the "create issue" operation optional. |
| Description |
Original:
h3. Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the h3. Steps to Reproduce * Log in as a Jira admin; * Access the "Manage Apps" section; * Click *+ Build a new app*; h3. Expected Results * Jira opens the correct page for this functions. h3. Actual Results * Jira throws a 404 error instead. h3. Workaround(s) * There is none. |
New:
h3. Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the screen used by the "create issue" operation, a screen will pop up so that the user fills the data for the required field. In this moment, Jira won't remember which subtask issue type the user has previously selected. You can view the following video about this: [^ h3. Steps to Reproduce * Access an issue (that is not a subtask) using the New Jira Issue View; * Be sure you have multiple subtask issue types available; * Be sure you select a subtask issue type which has a required field in the screen used by the "create issue" operations; * Select a random subtask issue type * Try to create a new subtask, filling the Summary field; h3. Expected Results * Jira will open a popup, and the random subtask issue type selected. h3. Actual Results * Jira will open a popup with the first subtask issue type available h3. Workaround(s) * Although probably not feasible, a workaround would be admins to make the field in the screen used by the "create issue" operation optional. |
| Attachment | New: JRACLOUD-71782.mp4 [ 344811 ] |
| Description |
New:
h3. Summary
In the New Jira Issue View, when the user clicks to create a subtask within a task, an "inline issue creator" will open for the user to create the subtask. If the subtask is using a field configuration which requires a field and that field is mapped to the h3. Steps to Reproduce * Log in as a Jira admin; * Access the "Manage Apps" section; * Click *+ Build a new app*; h3. Expected Results * Jira opens the correct page for this functions. h3. Actual Results * Jira throws a 404 error instead. h3. Workaround(s) * There is none. |