-
Suggestion
-
Resolution: Unresolved
-
None
-
Shipped standalone Tomcat
-
24
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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:
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.
- is related to
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-23590] Support pre-populating issue fields on CreateIssue.jspa
this seems like a no brainer, should be made part of the design. its very cumbersome otherwise to share default questions which we can add to the description now
Using "CreateIssueDetails!init.jspa" shows permanently validation errors on required fields - if you fill those fields - the validation errors not disappear but you can submit the form. You can not to fill fields by adding arguments in link by using "CreateIssue.jspa". Issue collector required default user to be set and user has to manually add his email what is also the unwanted feature. All tickets untouched or closed - it time to polish this area.
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.
If I try adding !init.jspa? to the string as suggested above, it does not assume the current logged in user is the reporter, and the Jira page that opens warns a reporter is required.
hubbitus solution works (for me) if you have one field that is required but not given in the issue it will not directly create the issue but let you edit the fields - yes it is a work around but available today.
@hubbitus No thats not the solution because the issue should not be created directly instead some fields should be assigned with default values and the user can edit all fields before creating the issue.
Is not https://confluence.atlassian.com/jirakb/how-to-create-issues-using-direct-html-links-in-jira-server-159474.html describe exactly what you want?
Hello all!
I try today in DC Jira version:
This is working on my site to prepopulate fields when create a issue:
So, 1kThanks b110fa26e2e4 added a comment - 24/Mar/2022 3:54 PM
BR
Melker