• 47
    • 47
    • 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 Cloud. Using JIRA Server? See the corresponding suggestion.

      There is currently no way to prepopulate some of the fields in the "Create Issue" page, so the user gets the standard form to fill in his issue details but some of the fields are pre-populated. Ideally that would be possible by passing the fields as UTF-8 encoded URL params to the create issue URL like that:

      http://jira.atlassian.com/secure/CreateIssue.jspa?pid=10240&issuetype=2&Create=Create&summary=A+wonderful+title&description=something+more

      This is currently not working. In contrast, it's easily possible to create whole issues, but for this case the user cannot change or add information. For our specific case, the use-case is:

      We are using JIRA not only for support but also as submission tool for data publications, supplementary to conventional academic articles (see www.pangaea.de). The user can create an issue and fill in the authors, title, abstract, license of the academic article and submit the supplementary data to us using JIRA. The JIRA issue is used to track the changes and workflows of the data submission. Often this information can be partly prepopulated on issue creation from e.g. an article citation, library catalogues,... This is especially relevant for invoking CreateIssue.jspa from a library catalogue and just wants to add data to the article at our place. In this case, lots of information on the Create Issue page can be pre-populated, but the user should be able to modify and complete the information.

      We have seen the confluence page about creating an issue with all fields filled out, but in that case we want to probvide the user the standard create issue form (where he can edit/enter the details) before creating the issue. Just a few fields should be prepopulated.

      This should be easily possible by modifying the JSP page to simply pre-populate the value="" of the <input> fields based on the URL parameters.

            [JRACLOUD-23590] Support pre-populating issue fields on CreateIssue.jspa

            hi,

            we are using this capability to prepopulate custom fields when they are created from confluence.. we embed a confluence macro on the confluence page and when user wants to create new story in Jira he  click the user macro button to create new story in Jira and some of the fields are being prepopulated using such URL - https://pdc-amat.atlassian.net/secure/CreateIssue.jspa?issuetype=10011&pid=10007&reporter=e173270&customfield_10612=BF-148184&customfield_10161=27212007773

             

            Erez Marcovich added a comment - hi, we are using this capability to prepopulate custom fields when they are created from confluence.. we embed a confluence macro on the confluence page and when user wants to create new story in Jira he  click the user macro button to create new story in Jira and some of the fields are being prepopulated using such URL - https://pdc-amat.atlassian.net/secure/CreateIssue.jspa?issuetype=10011&pid=10007&reporter=e173270&customfield_10612=BF-148184&customfield_10161=27212007773  

            Hi all,

            You may be interested in voting/watching/comment on below suggestion, which is for the same page that is referred to in this suggestion.

            JSWCLOUD-23788 Upgrade the page createissue.jspa to new issue view.

            The objective of the above is purely to upgrade the page to the new issue view, in line with the rest of Jira, but it would still be useful per current suggestion to be able to pre-populate more fields, not just project and type, as seems to be the case currently. This is just FYI.

            Ivan Shtanichev added a comment - Hi all, You may be interested in voting/watching/comment on below suggestion, which is for the same page that is referred to in this suggestion. JSWCLOUD-23788 Upgrade the page createissue.jspa to new issue view. The objective of the above is purely to upgrade the page to the new issue view, in line with the rest of Jira, but it would still be useful per current suggestion to be able to pre-populate more fields, not just project and type, as seems to be the case currently. This is just FYI.

            Having the ability to provide "default" values in the Description field would be a great help. We use the CreateIssue.jspa to create production support tickets and clients create a random description in the Description field. Would be great if we could pre-fill with "Desc, Steps to duplicate, impacted clientID, etc..." 

            Michael McLaughlin added a comment - Having the ability to provide "default" values in the Description field would be a great help. We use the CreateIssue.jspa to create production support tickets and clients create a random description in the Description field. Would be great if we could pre-fill with "Desc, Steps to duplicate, impacted clientID, etc..." 

            Grégory Verron added a comment - - edited

            Grégory Verron added a comment - - edited Hello Karl, for the moment, I suggest this workaround that works fine on my cloud instance: https://community.atlassian.com/t5/Jira-Core-Server-questions/How-to-create-a-template-for-issue-description/qaq-p/1041636 https://community.atlassian.com/t5/Jira-questions/Default-text-for-Description-field-on-Jira-Cloud/qaq-p/785597

            Karl A. added a comment -

            it's 2022 and this very basic feature is still not available, is there any plan to implement it soon?

            Karl A. added a comment - it's 2022 and this very basic feature is still not available, is there any plan to implement it soon?

            +1 

            Very useful. Please add that functionality on Cloud!!

            Olga Buslovich added a comment - +1  Very useful. Please add that functionality on Cloud!!

            Daniel added a comment -

            This was possible on Jira Server. It's a real let down that Cloud doesn't support it!

            Daniel added a comment - This was possible on Jira Server. It's a real let down that Cloud doesn't support it!

            +1

            BushIT added a comment -

            +1

            BushIT added a comment - +1

            +1

            Renuka.Raman added a comment - +1

              7645729f7e9f Arbaaz Gowher (Inactive)
              dc54674add53 Uwe Schindler
              Votes:
              190 Vote for this issue
              Watchers:
              121 Start watching this issue

                Created:
                Updated: