Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6488

The "Past Approvals" section does not display in the customer portal

      Issue Summary

      When an issue has been approved multiple times in the past, the issue displays a "Past Approvals" section when viewed as an Agent in Jira.

      Prior to Service Desk 4 (or 4.1, unsure on introduced version), this "Past Approvals" section was also shown on the customer portal.

      After upgrading to Service Desk 4, the "Past Approvals" section is not shown.

      Steps to Reproduce

      1. In Service Desk 3.x, create an issue that can be approved multiple times
      2. Verify the "Past Approvals" section shows up in the portal
      3. Upgrade to Service Desk 4.x

      Expected Results

      The "Past Approvals" section is displayed in the customer portal.

      Actual Results

      The "Past Approvals" section is not displayed in the customer portal.

      Workaround

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

            [JSDSERVER-6488] The "Past Approvals" section does not display in the customer portal

            After doing some more digging, we've discovered that this was an intentional choice made at the Jira Service Desk 3.10 release - to only show the current state of approval. As such, this issue is not a technical regression, although we can appreciate that there are folks who would like the old functionality back.

            As such, we'll update JSDSERVER-5679 and re-open it, to make sure that it covers the use cases correctly.

            Cheers,
            Dave
            Atlassian Support

            Dave Norton added a comment - After doing some more digging, we've discovered that this was an intentional choice made at the Jira Service Desk 3.10 release - to only show the current state of approval. As such, this issue is not a technical regression, although we can appreciate that there are folks who would like the old functionality back. As such, we'll update JSDSERVER-5679 and re-open it, to make sure that it covers the use cases correctly. Cheers, Dave Atlassian Support

              Unassigned Unassigned
              dnorton@atlassian.com Dave Norton
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: