-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
When using Create Linked Issue modal from a service project to another software project, with differing Issue Security Schemes, the modal populates the currently set security level from the originating service project.
The security levels from the selected destination project are seen when expanding the dropdown menu.
How to Replicate
- Setup JSM & JSW project with different Issue security schemes / security level(s) and set the Default Security Levels.
- Create test issue in JSM project and set security level.
- Trigger Create Linked Issue + modal within the test issue.
- Select JSW software project with active different security scheme.
- Review the issue security level value populated in the modal and expand the dropdown.
Expected Results
The Default security level from the destination project is populated in the Security Level field.
Actual Results
The currently set security level is populated, which will result in an inaccessible issue in the destination project.
Workaround
The security levels from the destination project are available when expanding the dropdown menu, which requires the user to select the next value in the list and be aware of the levels in the destination project.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-80498] Create linked issue modal in Issue view does not populate the default security level from the destination project security scheme
| Remote Link | New: This issue links to "Page (Confluence)" [ 734095 ] |
| Resolution | New: Obsolete [ 11 ] | |
| Status | Original: Short Term Backlog [ 12074 ] | New: Closed [ 6 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
When using _Create Linked Issue_ modal from a service project to another software project, with differing Issue Security Schemes, the modal populates the currently set security level from the originating service project. The security levels from the selected destination project are seen when expanding the dropdown menu. h3. How to Replicate # Setup JSM & JSW project with different Issue security schemes / security level(s) and set the Default Security Levels. # Create test issue in JSM project and set security level. # Trigger _Create Linked Issue +_ modal within the test issue. # Select JSW software project with active different security scheme. # Review the issue security level value populated in the modal and expand the dropdown. h3. Expected Results The Default security level from the destination project is populated in the Security Level field. h3. Actual Results The currently set security level is populated, which will result in a non-accessible issue in the destination project. h3. Workaround The security levels from the destination project are available when expanding the dropdown menu, which requires the user to select the next value in the list and be aware of the levels in the destination project. |
New:
h3. Issue Summary
When using _Create Linked Issue_ modal from a service project to another software project, with differing Issue Security Schemes, the modal populates the currently set security level from the originating service project. The security levels from the selected destination project are seen when expanding the dropdown menu. h3. How to Replicate # Setup JSM & JSW project with different Issue security schemes / security level(s) and set the Default Security Levels. # Create test issue in JSM project and set security level. # Trigger _Create Linked Issue +_ modal within the test issue. # Select JSW software project with active different security scheme. # Review the issue security level value populated in the modal and expand the dropdown. h3. Expected Results The Default security level from the destination project is populated in the Security Level field. h3. Actual Results The currently set security level is populated, which will result in an inaccessible issue in the destination project. h3. Workaround The security levels from the destination project are available when expanding the dropdown menu, which requires the user to select the next value in the list and be aware of the levels in the destination project. |
| Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 730835 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 730808 ] |
| Assignee | New: Ayush Rangwala [ a5dd1fdf76de ] |
Hey all, we’ve rolled back the release that introduced this bug in the Create linked issue screen. We appreciate your patience while we work on them. Please watch
JRACLOUD-60483to be notified when the new Create linked issue screen is released again.Thank you,
Arbaaz Gowher
Product Manager, Jira Cloud