Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-13193

Changing approvers on an issue with multiple approval steps appears to change approval history in the Customer Portal for earlier approvals.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Low
    • Approvals
    • None

    Description

      Issue Summary

      When a ticket is approved and transitions from one status that needs approval to the next, the name of the people who are added in the Approvers field is copied over and is visible in the customer portal for all previous statuses. We wipe the Approvers field empty after each status transition to remove the previous people. Each new name added sticks around to all previous statuses until the ticket is closed. That's when only the names who approved are kept as "history".

      Steps to Reproduce

      1. Create a Workflow or Modify the Approvals Workflow to Include a 2nd Approval Step.
      2. Ensure the Same Approvers Field is used for the Approve Step in both the Approval Status ( Select All Status can Transition to Speed up the process )
      3. Publish the Workflow and then create a test ticket from the Portal; Add an Approver ( Example: ABC ) 
      4. Login as ABC and Approve - > Transition to 2nd Workflow Steps
      5. Manually; Clear the Approver Field and Replace it with another User ( Example XYC ) 
      6. Login as XYC and Approve. 
      7. Once approved login to the customer portal and you will see that XYC is also seen in Approval Step 1.

      Expected Results

      The request should display the Approvers who approved in previous status.

      Actual Results

      The approver's name and the new approver's name are visible on the customer portal for previous approvals.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

      Attachments

        Activity

          People

            Unassigned Unassigned
            a5efd6340a5c Abishek .
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: