I want a way for users to submit requests that results in an issue being created automatically with the various fields (i.e. Epic Link, Component, Fix Version, etc.) filled out according to their respective submissions. Meaning, user inputs are collected via pre-selected options in a drop down menu &/or Radio buttons. Free-form text will not be used except for the Summary/Description.
To get this out of the way, I am working in a Jira Software project space so the Issue Collector feature will not work.
Currently, I have an Intake form in Confluence that has been mapped to Jira via email. This results in a Jira issue created systemically, however, all of the details provided in the intake form appear in the description of the newly created issue. Meaning I, or someone on my team, has to manually update each issue after it is created. Not the most strategic solution. I work in a very large organization with a high volume of requests. Manual work such as this is not a viable option. Any help is appreciated.
@Chad Wood Welcome to the Atlassian community
You will need to use the Jira API. This will allow you to create issue via the API and map fields to custom fields and only allow them to make specific selections.
https://developer.atlassian.com/server/jira/platform/rest/v10000/intro/#gettingstarted
@Chad Wood Do you have to have confluence to use this form type? My company has our own internal hub that is not on confluence and wondering if I can use the api creation from there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Natalie. For the type of form that I used, Confluence is required with a back end email to Jira connection. If you don't have access to Confluence then it might be in your best interest to explore the API route.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use Smart Forms for Jira to streamline your process. It lets you:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To add on to this for anyone that happens to stumble upon this page. I modified the Confluence intake form and set up automation rules in Jira to update the newly created issue systemically. This has helped my workflow but it is far from perfect. The data from the form still populates the description but at least I have some of the fields automatically updated so the new stories are bucketed appropriately.
I am looking into the API option that was suggested by Brant and will update this post if I am able to make any progress.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.