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

Fill out hostname of customer when he is creating an issue

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 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.

      Our current ticketing system can automtatically fill out the hostname (PC-Client Name) field of the ticket when a customer creates a new ticket. Is there a way for JIRA Service Desk to get that information?

      It is needed by our client support team so they know what client is affected by whatever problem is reported by the customer and letting the customer fill out the hostname manually is not that reliable.

            [JSDSERVER-4491] Fill out hostname of customer when he is creating an issue

            Alex Cooksey (Inactive) made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Charlie Marriott added a comment -
            Atlassian Update – 1 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,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 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, Jira Service Management, Server & Data Center
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011801 ] New: JAC Suggestion Workflow 3 [ 3647153 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665223 ] New: JAC Suggestion Workflow [ 3011801 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324297 ] New: Confluence Workflow - Public Facing v4 [ 2665223 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053147 ] New: JSD Suggestion Workflow - TEMP [ 2324297 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048186 ] New: JSD Suggestion Workflow [ 2053147 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1622020 ] New: JSD Suggestion Workflow - TEMP [ 2048186 ]
            jonah (Inactive) made changes -
            Description Original: Our current ticketing system can automtatically fill out the hostname (PC-Client Name) field of the ticket when a customer creates a new ticket. Is there a way for JIRA Service Desk to get that information?

            It is needed by our client support team so they know what client is affected by whatever problem is reported by the customer and letting the customer fill out the hostname manually is not that reliable.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4491].
              {panel}

            Our current ticketing system can automtatically fill out the hostname (PC-Client Name) field of the ticket when a customer creates a new ticket. Is there a way for JIRA Service Desk to get that information?

            It is needed by our client support team so they know what client is affected by whatever problem is reported by the customer and letting the customer fill out the hostname manually is not that reliable.

              Unassigned Unassigned
              18e95264fd9d Jonathan
              Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: