-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
None
-
None
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Steps to Reproduce:
- Create a new dummy Service Desk project.
- Create a new dummy Customer user.
- Login to the Customer portal using the dummy Customer and create a ticket.
- Back to JIRA and login as Agent of the Service Desk project.
- Go to the ticket and "Respond to Customer" to change the status.
- Login back to the Customer Portal and respond to the ticket as Customer.
Expected Result:
- The status beside the summary will change.
Actual Result:
Notes:
- duplicates
-
JSDSERVER-1752 Automatic transitions are not visible to Customers without a refresh
-
- Closed
-
- relates to
-
JSDCLOUD-1824 At the Customer Portal, Status is not automatically refreshed after comment
-
- Closed
-
[JSDSERVER-1824] At the Customer Portal, Status is not automatically refreshed after comment
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305225 ] | New: JAC Bug Workflow v3 [ 3124924 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2059166 ] | New: JSD Bug Workflow v5 - TEMP [ 2305225 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056570 ] | New: JSD Bug Workflow v5 [ 2059166 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956200 ] | New: JSD Bug Workflow v5 - TEMP [ 2056570 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1614607 ] | New: JSD Bug Workflow v5 [ 1956200 ] |
Description |
Original:
*Steps to Reproduce:*
# Create a new dummy Service Desk project. # Create a new dummy Customer user. # Login to the Customer portal using the dummy Customer and create a ticket. # Back to JIRA and login as Agent of the Service Desk project. # Go to the ticket and "Respond to Customer" to change the status. # Login back to the Customer Portal and respond to the ticket as Customer. *Expected Result:* * The status beside the summary will change. *Actual Result:* * The status did not change. !JSD241.gif|thumbnail! *Notes:* * This is tested on JSD 2.4.1 while on JSD 2.2.0 it will automatically changed per comment. * On JSD 2.2.0 Automation is not introduced yet. It is still using "legacy automatic transitions". !JSD220.gif|thumbnail! |
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-1824]. {panel} *Steps to Reproduce:* # Create a new dummy Service Desk project. # Create a new dummy Customer user. # Login to the Customer portal using the dummy Customer and create a ticket. # Back to JIRA and login as Agent of the Service Desk project. # Go to the ticket and "Respond to Customer" to change the status. # Login back to the Customer Portal and respond to the ticket as Customer. *Expected Result:* * The status beside the summary will change. *Actual Result:* * The status did not change. !JSD241.gif|thumbnail! *Notes:* * This is tested on JSD 2.4.1 while on JSD 2.2.0 it will automatically changed per comment. * On JSD 2.2.0 Automation is not introduced yet. It is still using "legacy automatic transitions". !JSD220.gif|thumbnail! |
Link |
New:
This issue relates to |
Workflow | Original: JSD Bug Workflow v2 [ 1601949 ] | New: JSD Bug Workflow v4 [ 1614607 ] |
Workflow | Original: JSD Bug Workflow [ 1397961 ] | New: JSD Bug Workflow v2 [ 1601949 ] |
Workflow | Original: TTT: Simple Issue Tracking Workflow [ 856949 ] | New: JSD Bug Workflow [ 1397961 ] |