Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-1330

Showing Issue Key in the Customer Portal

XMLWordPrintable

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

        1. portal.png
          portal.png
          54 kB

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

            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

            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

            Adam Morrison added a comment -

            Thanks for this Atlassian! Looks great.

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

            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?

            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.

            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!

            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!

            Okan Tasdelen added a comment -

            Any update on this?

            Okan Tasdelen added a comment - Any update on this?

            Richard Bergmann added a comment -

            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!

            Jakob Stoltz added a comment -

            +1
            Any news or updates from Atlassian on this?

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

            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?

            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?

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

                Created:
                Updated:
                Resolved: