-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.4-OD-05, 2.5.0, 3.3.0, 3.9.0, 3.9.1, 3.9.7
-
11
-
Severity 3 - Minor
-
2
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Atlassian Update – 9 June 2021
Hi everyone,
Thank you for your interest in this suggestion.
We have identified that this is a duplicate of "Auto-refresh and/or warn user if the ticket has changed" JSDSERVER-433. We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates.
Kind regards,
Alex
Jira Service Management, Server & Data Center
When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made.
That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status.
This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need.
- duplicates
-
JSDSERVER-433 Auto-refresh and/or warn user if the ticket has changed
- Gathering Interest
- is detailed by
-
- Closed
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
- causes
-
CST-13108 Loading...
- was cloned as
-
(1 causes, 3 mentioned in, 1 was cloned as)
[JSDSERVER-1752] Automatic transitions are not visible to Customers without a refresh
| Link | New: This issue duplicates JSDSERVER-433 [ JSDSERVER-433 ] |
| Link | Original: This issue is related to JSDSERVER-433 [ JSDSERVER-433 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 9 June 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 9 June 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433. We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 19 June 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 9 June 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 9 June 2021} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 19 June 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1752]. {panel} {panel:title=Atlassian Update – 9 June 2021} Hi everyone, Thank you for your interest in this suggestion. We have identified that this is a duplicate of _"Auto-refresh and/or warn user if the ticket has changed"_ JSDSERVER-433 . We are actively reviewing this suggestion and will continue to track interest on the other ticket. Please watch JSDSERVER-433 for future updates. Kind regards, Alex Jira Service Management, Server & Data Center {panel} When we have an issue in 'Waiting for Customer' status and the customer triggers the transition to 'Waiting for Support' by commenting on the issue, the customer's comment is added, but the page is not refreshed after the transition is made. That results in the page showing the old status (Waiting for Customer) and the customer has to refresh the page to see the new status. This makes the customers confused, as it is not clear that the transition was correctly triggered. They escalate or raise new cases which steals time from getting them the support they need. |
| Comment | [ A comment with security level 'atlassian-staff' was removed. ] |
| Link | New: This issue is related to JSDSERVER-433 [ JSDSERVER-433 ] |
| UIS | Original: 0 | New: 2 |