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

Display the "Past Approvals" panel in the Customer Portal View of a Request

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Customer Portal
    • None
    • 0
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary

      In versions of Jira Service Desk before 3.10, the "Past Approvals" section was shown in the customer portal, making it clear to customers who had approved the issue in the past.

      As of Service Desk 3.10, only the current approval action is shown in the portal. The Jira UI consistently shows the current action, as well as the past actions:

      From Jira's UI:

      From Service Desk Portal:

      Proposed Solution

      Provide a toggle for administrators to show the past approvals section in the customer portals. Not all admins may want this functionality, but those who relied on it previously should have the option to use it again.

        1. From_CustomerPortal.png
          From_CustomerPortal.png
          130 kB
        2. From_JIRAUI.png
          From_JIRAUI.png
          245 kB

            [JSDSERVER-5679] Display the "Past Approvals" panel in the Customer Portal View of a Request

            Atlassian Update – 5 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 5 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Charlie Jira Service Management, Server & Data Center

            We've done a bit more digging on this, and we've discovered that this was an actual change made in Jira Service Desk 3.10, so it's actually not a regression. As such, we'll re-open this feature request, and clarify that we're looking for a toggle for admins to use which behaviour they find better for their use case.

            Cheers,
            Dave
            Atlassian Support

            Dave Norton added a comment - We've done a bit more digging on this, and we've discovered that this was an actual change made in Jira Service Desk 3.10, so it's actually not a regression. As such, we'll re-open this feature request, and clarify that we're looking for a toggle for admins to use which behaviour they find better for their use case. Cheers, Dave Atlassian Support

            Hi dtheodore,

            Apologies for the delay in getting back to you here. After consulting with the development team on this for another customer, we've confirmed this is a regression that's being tracked over at JSDSERVER-6488. I had to create a new bug as I couldn't just clone this as a bug. I'll close this one as a duplicate, and we'll follow the bug process there.

            The development team are looking into when this issue can be fixed, so please make sure you're following the new report for further updates.

            Cheers,
            Dave
            Senior Support Engineer (Sydney)

            Dave Norton added a comment - Hi dtheodore , Apologies for the delay in getting back to you here. After consulting with the development team on this for another customer, we've confirmed this is a regression that's being tracked over at JSDSERVER-6488 . I had to create a new bug as I couldn't just clone this as a bug. I'll close this one as a duplicate, and we'll follow the bug process there. The development team are looking into when this issue can be fixed, so please make sure you're following the new report for further updates. Cheers, Dave Senior Support Engineer (Sydney)

            This is really not a suggestion.  The product had this feature in the past (3.2.8/7.2.8 has this functionality.) Cloud currently has it. There was a regression on Server where this functionality was removed.

            Dave Theodore [Coyote Creek Consulting] added a comment - This is really not a suggestion.  The product had this feature in the past (3.2.8/7.2.8 has this functionality.) Cloud currently has it. There was a regression on Server where this functionality was removed.

              Unassigned Unassigned
              jrey Julien Rey
              Votes:
              6 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: