-
Bug
-
Resolution: Cannot Reproduce
-
Low (View bug fix roadmap)
-
None
-
8.3.3, 8.9.0
-
None
-
8.03
-
Severity 3 - Minor
-
Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected).
This was reported via the Atlassian community: https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476
Steps to Reproduce
- Create an agent who does not have access to view issues when they are in a particular status
- You can achieve this by editing workflow and adding "jira.permission.browse.group = some-group" in the status properties. Also some other useful info can be found here.
- Create a transition which transitions issues to the status above which the agent cannot view
- As the agent transition the issue to this status
- Observe the page stuck loading (should not happen)
- Refresh and observe the permissions error (expected)
Expected Results
Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on.
Actual Results
The agent is stuck on a loading page.
Workaround
Refresh and then redirect back to the portal
- mentioned in
-
Page Failed to load
[JRASERVER-71140] When an agent transitions an issue to a status they do not have permission to, they are stuck on a loading page
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Description |
Original:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). This was reported via the Atlassian community: [https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476] h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status ## You can achieve this by editing workflow and adding "jira.permission.browse.group = some-group" in the status properties. # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
New:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). This was reported via the Atlassian community: [https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476] h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status ## You can achieve this by editing workflow and adding "jira.permission.browse.group = some-group" in the status properties. Also some other useful info can be found [here|https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status]. # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
| Description |
Original:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). This was reported via the Atlassian community: [https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476] h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
New:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). This was reported via the Atlassian community: [https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476] h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status ## You can achieve this by editing workflow and adding "jira.permission.browse.group = some-group" in the status properties. # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
| Introduced in Version | Original: 8.09 | New: 8.03 |
| Affects Version/s | New: 8.3.3 [ 88609 ] |
| Introduced in Version | New: 8.09 |
| Description |
Original:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
New:
h3. Issue Summary
When the admin creates a transition which limits the visibility of an issue, the agents getting stuck on a loading screen. When the agent then refreshes the page, the are presented with a permissions error (as expected). This was reported via the Atlassian community: [https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-redirect-agent-to-custom-screen-after-transition/qaq-p/1335476] h3. Steps to Reproduce # Create an agent who does not have access to view issues when they are in a particular status # Create a transition which transitions issues to the status above which the agent cannot view # As the agent transition the issue to this status # Observe the page stuck loading (should not happen) # Refresh and observe the permissions error (expected) h3. Expected Results Agent is redirect to the portal home page, or allow the transition to define a redirect page to land on. h3. Actual Results The agent is stuck on a loading page. h3. Workaround Refresh and then redirect back to the portal |
| Remote Link | New: This issue links to "Page (Confluence)" [ 487519 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 487518 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 487518 ] |