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

      At the moment, Customer can see his/her issue request by referring to the issue summary. There is no issue-key shown in the customer portal.

      Since issue key is the most referred information of an issue in JIRA, it's better to have the issue key to be shown in the customer portal.
      Customers may have a lot of issues in the customer portal which have similar title/issue summary. Having the issue key shown in the customer portal will ease the searching process to get the exact issue.

            [JSDCLOUD-1330] Showing Issue Key in the Customer Portal

            dave.nash

            This feature was implemented in version 3.1.0 of JIRA Service Desk for Server.

            Cheers!
            Joao

            Joao Palharini (Inactive) added a comment - dave.nash This feature was implemented in version 3.1.0 of JIRA Service Desk for Server. Cheers! Joao

            Thanks for this Atlassian! Looks great.

            Adam Morrison added a comment - Thanks for this Atlassian! Looks great.

            So this looks useful for cloud - any news on which version this has/will be implemented on the server model?

            David Nash (inactive) added a comment - So this looks useful for cloud - any news on which version this has/will be implemented on the server model?

            vwong added a comment -

            This feature is released on JIRA Service Desk 3.1.0-OD-10.
            Release notes for this feature can be found here: https://confluence.atlassian.com/display/SERVICEDESKCLOUD/2016/01/08/Improved+My+Requests+page

            vwong added a comment - This feature is released on JIRA Service Desk 3.1.0-OD-10. Release notes for this feature can be found here: https://confluence.atlassian.com/display/SERVICEDESKCLOUD/2016/01/08/Improved+My+Requests+page

            John Desha added a comment -

            This request is also duplicated by JSD-393, JSD-652, JSD-1106, JSD-1204, JSD-1615, and JSD-1777 (and those are just the open ones, more have already been closed as duplicates).

            I am starting to become baffled by the lack of response from anyone at Atlassian. Even a "not a bad idea, we'll look into it" comment would be better than pure silence.

            John Desha added a comment - This request is also duplicated by JSD-393 , JSD-652 , JSD-1106 , JSD-1204 , JSD-1615 , and JSD-1777 (and those are just the open ones, more have already been closed as duplicates). I am starting to become baffled by the lack of response from anyone at Atlassian. Even a "not a bad idea, we'll look into it" comment would be better than pure silence.

            Come on Atlassian - surely the Key is an essential part of the customer portal - how are we supposed to reference the issue with the customer in correspondence? Respond please and let us know when this is going to be implemented.

            This cannot be a difficult thing to do!

            Matt Illston added a comment - Come on Atlassian - surely the Key is an essential part of the customer portal - how are we supposed to reference the issue with the customer in correspondence? Respond please and let us know when this is going to be implemented. This cannot be a difficult thing to do!

            Any update on this?

            Okan Tasdelen added a comment - Any update on this?

            A solution to this problem would indeed be very helpful!

            Richard Bergmann added a comment - A solution to this problem would indeed be very helpful!

            +1
            Any news or updates from Atlassian on this?

            Jakob Stoltz added a comment - +1 Any news or updates from Atlassian on this?

            +1

            It's confusing for customers when they have to raise tickets for more than one product which are effectively the same change and/or titled the same way. It's not immediately obvious which product this is for.

            My assumption is that this is a relatively trivial change to make for Atlassian and shouldn't take weeks or months to implement.
            Could it please be prioritised to enhance our, and obviously others', customers' experience and therefore create a better buy-in for the service desk experience for both the customers and the help desk agents?

            Michael Blake added a comment - +1 It's confusing for customers when they have to raise tickets for more than one product which are effectively the same change and/or titled the same way. It's not immediately obvious which product this is for. My assumption is that this is a relatively trivial change to make for Atlassian and shouldn't take weeks or months to implement. Could it please be prioritised to enhance our, and obviously others', customers' experience and therefore create a better buy-in for the service desk experience for both the customers and the help desk agents?

            +1 Please could serious consideration be given to this request.
            The idea of having to manually add the issue number to the subject of each request is tedious and time consuming.
            This would be a great enhancement as the Customers most often refer to an issue number as there could be duplicate naming conventions which could cause confusion.

            Lucille Green added a comment - +1 Please could serious consideration be given to this request. The idea of having to manually add the issue number to the subject of each request is tedious and time consuming. This would be a great enhancement as the Customers most often refer to an issue number as there could be duplicate naming conventions which could cause confusion.

            SisavanhS added a comment -

            +1 agree with Karel, this is really a missing information for the list view and the search.
            We currently workaround it by setting the issue ID in the title but that is not convenient to do it for each issue.
            At least is there a way to customize the the portal ? Any template where we can add custom information ?
            Thanks for the feedbacks.

            SisavanhS added a comment - +1 agree with Karel, this is really a missing information for the list view and the search. We currently workaround it by setting the issue ID in the title but that is not convenient to do it for each issue. At least is there a way to customize the the portal ? Any template where we can add custom information ? Thanks for the feedbacks.

            This is definitely a feature that most users of the Customer Portal would need - especially those who log a large number of requests for support or development. As mentioned above, it isn't always possible to reference an issue by the subject alone, as many can be repetitious and hard to tell between except if you use a unique identifier.

            Cheryl Childs [Dreamsmiths] added a comment - This is definitely a feature that most users of the Customer Portal would need - especially those who log a large number of requests for support or development. As mentioned above, it isn't always possible to reference an issue by the subject alone, as many can be repetitious and hard to tell between except if you use a unique identifier.

            KarelH added a comment -

            Even though issue key is shown on view request page, it's not show on issue list in My Requests page. When discussing requests, they are referenced by their only unique identifier - issue ID. Combined with the fact that you cannot search by issue ID, this is a problem (as you cannot even use browser search functionality to quickly find the issue on the page).

            KarelH added a comment - Even though issue key is shown on view request page, it's not show on issue list in My Requests page. When discussing requests, they are referenced by their only unique identifier - issue ID. Combined with the fact that you cannot search by issue ID, this is a problem (as you cannot even use browser search functionality to quickly find the issue on the page).

            What Andreas says.

            At least the searchresults should rerturn tickets if the corresponding issue ID is used. Even better would be if the issue ID is shown on the 'my results' page.

            Thanks in advance.

            hajo.van.ravenswaay added a comment - What Andreas says. At least the searchresults should rerturn tickets if the corresponding issue ID is used. Even better would be if the issue ID is shown on the 'my results' page. Thanks in advance.

            @Panna Cherukuri [Atlassian]: But not on Overview. When we talk about an issue, we use the issue ID. It is very helpful to see the ID and summary to find quickly the affected issue.

            Andreas Beekma added a comment - @Panna Cherukuri [Atlassian] : But not on Overview. When we talk about an issue, we use the issue ID. It is very helpful to see the ID and summary to find quickly the affected issue.

            Issue key is shown on the View request page already.

            Panna (Inactive) added a comment - Issue key is shown on the View request page already.

              Unassigned Unassigned
              azuhra Aqqiela
              Votes:
              67 Vote for this issue
              Watchers:
              47 Start watching this issue

                Created:
                Updated:
                Resolved: