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

      Atlassian Update – 18 February 2022

      Hi everyone,

      Thank you for your interest in this issue.

      We have shipped support for auto-populated request fields in Jira Service Management Data Center 4.22.

      You can generate URLs that will automatically populate selected request fields with contextual data. This way you can direct your customers to the customer portal from an external website and transfer certain details into the request fields.

      Learn how to set up URLS with auto-populated request fields.

      Kind regards,

      Charlie

      Jira Service Management, Data Center & Server

      We receive requests for email promotions from our Atlassian User Group Leaders… They are (for the most part) canned emails. We would like to give them a template they can use, but also change if they would like to customize it.

      I think there are more use cases for this as well

            [JSDSERVER-133] Pre-filled values for fields in a request

            Atlassian Update – 18 February 2022

            Hi everyone,

            Thank you for your interest in this issue.

            We have shipped support for auto-populated request fields in Jira Service Management Data Center 4.22.

            You can generate URLs that will automatically populate selected request fields with contextual data. This way you can direct your customers to the customer portal from an external website and transfer certain details into the request fields.

            Learn how to set up URLS with auto-populated request fields.

            Kind regards,

            Charlie

            Jira Service Management, Data Center & Server

            Charlie Marriott added a comment - Atlassian Update – 18 February 2022 Hi everyone, Thank you for your interest in this issue. We have shipped support for auto-populated request fields in Jira Service Management Data Center 4.22 . You can generate URLs that will automatically populate selected request fields with contextual data. This way you can direct your customers to the customer portal from an external website and transfer certain details into the request fields. Learn how to set up URLS with auto-populated request fields . Kind regards, Charlie Jira Service Management, Data Center & Server

            Great to see status Waiting for Release Bravo!

            Gonchik Tsymzhitov added a comment - Great to see status Waiting for Release Bravo!

            It's possible to pre-fill hidden custom fields?

            Rodrigo Burigo added a comment - It's possible to pre-fill hidden custom fields?

            Will be happy to see in JSM (JSD) server release

            Gonchik Tsymzhitov added a comment - Will be happy to see in JSM (JSD) server release

            for love of dog get on with it

            Mat Stojanovic added a comment - for love of dog get on with it

            I have the same question about this, why has it been implemented on JSDCloud but not yet implemented in JSDServer?

            Jiahao Xiao added a comment - I have the same question about this, why has it been implemented on JSDCloud but not yet implemented in JSDServer?

            Ines B. added a comment - - edited

            It seems this is working for Cloud JSDCLOUD-4049  Is it only implemented for it or does it works for Server too?

            Ines B. added a comment - - edited It seems this is working for Cloud  JSDCLOUD-4049   Is it only implemented for it or does it works for Server too?

            Another Use case is for client request example:
            New User accounts:

            We have a pre-defined 'New User' issue type, they can click and start a ticket, It would even better for our clients if we could have the ticket description pre populated with all required data, as a method to ensure consistency and accuracy for our customers. (whether they are internal developers or external clients)

            Example: 
            Click new User Link from Service Desk:

            New ticket Opens: 

            Title: Customer X - New User Request

            Description: 
            NAME:
            PHONE:
            EMAIL:
            SUPERVISOR:
            ROLE/PERMISSION:
            SPECIAL PERMISSIONS:
            AGENCY:
            APPROVAL BY:

            christopher.butler added a comment - Another Use case is for client request example: New User accounts: We have a pre-defined 'New User' issue type, they can click and start a ticket, It would even better for our clients if we could have the ticket description pre populated with all required data, as a method to ensure consistency and accuracy for our customers. (whether they are internal developers or external clients) Example:  Click new User Link from Service Desk: New ticket Opens:  Title: Customer X - New User Request Description:  NAME: PHONE: EMAIL: SUPERVISOR: ROLE/PERMISSION: SPECIAL PERMISSIONS: AGENCY: APPROVAL BY:

            We really want this, makes it more easy to define repetitive requests with prefilled information. 

            Dominik Heim added a comment - We really want this, makes it more easy to define repetitive requests with prefilled information. 

            We need to automatically capture emails and some other metadata of users to save time for agents working on tickets. Is this suggestion going to ever become a story, Atlassian? 

            Elvin Badalov added a comment - We need to automatically capture emails and some other metadata of users to save time for agents working on tickets. Is this suggestion going to ever become a story, Atlassian? 

              cmarriott Charlie Marriott
              ezhang Ed Zhang (Automation)
              Votes:
              184 Vote for this issue
              Watchers:
              78 Start watching this issue

                Created:
                Updated:
                Resolved: