• 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.

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

      Scenario 1: Customer belongs to multiple JSDs
      Scenario 2: Customer has lots issues with different issue types

      It would be nice to allow customers to filter their requests on the 'My Requests' page per project or issue type. Today the options: All/Open/Closed requests and search for ticket title does not cover those scenarios if customer don't remember any of those but the project.

          Form Name

            [JSDSERVER-1663] Allow customers to filter My Requests

            Charlie Marriott made changes -
            Resolution Original: Done [ 17 ] New: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011586 ] New: JAC Suggestion Workflow 3 [ 3646787 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2664636 ] New: JAC Suggestion Workflow [ 3011586 ]

            As an Atlassian Platinum Enterprise Partner and a Gold Top Vendor leading the ITSM segment of the Ecosystem, we've also dealt with this limitation of Jira Service Desk Server and added My Requests Extension to our JSD app suite. It gives you, as an admin, the possibility to configure which fields can be displayed on My Requests page, which of them are visible as columns by default, and also define which user group can use a specific field. Then your customers can add, change and reorder the columns on My Requests page and filter issues by specific Service Desks, Organizations, Request types and Statuses.

            However, for now the app is available for Server only.

            For more details, please refer to the app's documentation or drop a line at support@deviniti.com.

            Katarzyna Pawlak [Deviniti] added a comment - As an Atlassian Platinum Enterprise Partner and a Gold Top Vendor leading the ITSM segment of the Ecosystem, we've also dealt with this limitation of Jira Service Desk Server and added  My Requests Extension  to our JSD app suite. It gives you, as an admin, the possibility to configure which fields can be displayed on My Requests page, which of them are visible as columns by default, and also define which user group can use a specific field. Then your customers can add, change and reorder the columns on My Requests page and filter issues by specific Service Desks, Organizations, Request types and Statuses. However, for now the app is available for Server only. For more details, please refer to the app's  documentation  or drop a line at  support@deviniti.com .

            As we believe this feature is a must for Jira Service Desk, we created an add-on to do it: https://marketplace.atlassian.com/apps/1219230/advanced-portal-reports-for-service-desk

            The Customer has to select a Service desk project to see the requests for it.

            It allows the Jira Service Desk project admin to decide which fields to be available for the Portal Customer to see, and the Customer can decide which of the allowed fields to show. There is an option to allow Customers to see all requests in the portal or only the ones that they should have access to. Export to CSV is available. Sorting by column and filtering are also there. 

            More features to be added soon. 

            Feedback is highly appreciated!

            Boyan Angelov (Nemetschek Bulgaria) added a comment - As we believe this feature is a must for Jira Service Desk, we created an add-on to do it:  https://marketplace.atlassian.com/apps/1219230/advanced-portal-reports-for-service-desk The Customer has to select a Service desk project to see the requests for it. It allows the Jira Service Desk project admin to decide which fields to be available for the Portal Customer to see, and the Customer can decide which of the allowed fields to show. There is an option to allow Customers to see all requests in the portal or only the ones that they should have access to. Export to CSV is available. Sorting by column and filtering are also there.  More features to be added soon.  Feedback is highly appreciated!
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2326060 ] New: Confluence Workflow - Public Facing v4 [ 2664636 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2054063 ] New: JSD Suggestion Workflow - TEMP [ 2326060 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049392 ] New: JSD Suggestion Workflow [ 2054063 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280692 ] New: JSD Suggestion Workflow - TEMP [ 2049392 ]

            Hi, some additions for this issue. Why it is not possible to manage My requests page by admin including different fields on the filter. My customers would like to se not all requests but to filter by versiones, components etc. It will be fine to develop My requests page by admin like different Queues filters are developed

            Andrey Galyapa added a comment - Hi, some additions for this issue. Why it is not possible to manage My r equests  page by admin including different fields on the filter. My customers would like to se not all requests but to filter by versiones, components etc. It will be fine to develop My r equests  page by admin like different Queues filters are developed

              Unassigned Unassigned
              ediel Elisa [Atlassian]
              Votes:
              17 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: