• 1
    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Actual

      In every JIRA you have Customers who also use JIRA for there projects. For this group of users it is hard to track there requests outside the customer portal if you give them only the permission to use the customer portal. They have already a dashboard to track their issues, but they lost the focus on there open Service Desk requests.

      It's much harder to keep an eye on your request if the user has access to multiple Service Desks.

      Exprected behaviour

      Create a new JIRA Gadget where users get an overview about their unresolved Service Desk Requests.
      Due to the SD 1.2 restrictions it is not possible to use the filter gadget.

      Update 24th November 2020

      We appreciate the merit of this issue, but don't intend to work it in the foreseeable future. We'll review it again within a year to see if our decision has changed.



      Thanks,

      JSM Team.

            [JSDCLOUD-365] Service Desk Gadgets for Customers

            Hello Atlassian, are there any updates on the lifecycle of this suggestion?

            My use case:

            We were heavy users of Jira Software for a few years now, and have recently added Service Desk to the stack. I have custom filters built for all users who show them issues pending their approval (custom-built functionality) across all projects, including purchasing and our old Help Desk project. I'm unable to include the Service Desk approval requests in their queue, which is causing a lot of missed approvals.

            I'm looking at creating a custom dashboard gadget to display current user's approval requests / outstanding requests, but it's a very inefficient workaround (which directly translates to: it costs me more money to run Atlassian products.) I think this is of high value for companies that use SD for internal help desk functionality on top of an existing Jira instance.

            Damian Rosochacki added a comment - Hello Atlassian, are there any updates on the lifecycle of this suggestion? My use case: We were heavy users of Jira Software for a few years now, and have recently added Service Desk to the stack. I have custom filters built for all users who show them issues pending their approval (custom-built functionality) across all projects, including purchasing and our old Help Desk project. I'm unable to include the Service Desk approval requests in their queue, which is causing a lot of missed approvals. I'm looking at creating a custom dashboard gadget to display current user's approval requests / outstanding requests, but it's a very inefficient workaround (which directly translates to: it costs me more money to run Atlassian products.) I think this is of high value for companies that use SD for internal help desk functionality on top of an existing Jira instance.

              jdcruz Jason D'Cruz
              4e81381d415c Tim Eddelbüttel
              Votes:
              27 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: