-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
9
-
3
-
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
For example, automation rules inspects a custom field on transition to status A. If the field has content, the issue is changes to B status. If the field is empty the status changes to C status.
Currently when users transition issues to status A they will initially see their issue in status A. Upon refresh the issue's status is correctly displayed as either B or C.
This request is for a mechanism that will auto-refresh an issue so that users will see the issue status after an automation rule takes effect
Workaround: Use JavaScript, looking for form elements that are unique to this condition, and refresh the page when true.
Notes: Also happen for adding comment from agent side.
- details
-
JSDSERVER-1752 Automatic transitions are not visible to Customers without a refresh
-
- Closed
-
- duplicates
-
JSDSERVER-433 Auto-refresh and/or warn user if the ticket has changed
- Gathering Interest
- is duplicated by
-
JSDSERVER-6106 Automatic transitions on adding comment are not visible to Agents without a refresh
-
- Closed
-
- mentioned in
-
Page Failed to load
[JSDSERVER-5452] Auto-refresh issue transitioned from Service Desk automation rule
Link | Original: This issue is related to JSDSERVER-433 [ JSDSERVER-433 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Link | New: This issue duplicates JSDSERVER-433 [ JSDSERVER-433 ] |
Description |
Original:
For example, automation rules inspects a custom field on transition to status A. If the field has content, the issue is changes to B status. If the field is empty the status changes to C status.
Currently when users transition issues to status A they will initially see their issue in status A. Upon refresh the issue's status is correctly displayed as either B or C. This request is for a mechanism that will auto-refresh an issue so that users will see the issue status after an automation rule takes effect Workaround: Use JavaScript, looking for form elements that are unique to this condition, and refresh the page when true. Notes: Also happen for adding comment from agent side. |
New:
{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} For example, automation rules inspects a custom field on transition to status A. If the field has content, the issue is changes to B status. If the field is empty the status changes to C status. Currently when users transition issues to status A they will initially see their issue in status A. Upon refresh the issue's status is correctly displayed as either B or C. This request is for a mechanism that will auto-refresh an issue so that users will see the issue status after an automation rule takes effect Workaround: Use JavaScript, looking for form elements that are unique to this condition, and refresh the page when true. Notes: Also happen for adding comment from agent side. |
Link | New: This issue is related to JSDSERVER-433 [ JSDSERVER-433 ] |
UIS | Original: 0 | New: 9 |
UIS | Original: 16 | New: 0 |
Remote Link | New: This issue links to "Page (Confluence)" [ 516693 ] |
UIS | Original: 24 | New: 16 |
UIS | Original: 16 | New: 24 |