JIRA: create an issue with pre-populated fields
β’ 250 words β’ 2 min β’ updated
It is somewhat tedious to create issues1 in JIRA. It is a bloated and complex web app, slow to load, with a myriad of fields to fill in.
Most of these input fields do not significantly change when working within a single team. The common exceptions are the Summary (Issue title) and Description. Priority and Assignee can be determined later on, during bug triage.
It turns out JIRA supports creating issues using direct links.
The documentation isn’t the most user-friendly2 but, upon figuring it out, you can build a URL such as:
https://{company}.atlassian.net/secure/CreateIssueDetails!init.jspa?pid={project-id}&issuetype=10003&summary=Component%3A%20Title&description=&customfield_10249=SRE&labels=quick-winNotes:
-
Project ID: you can figure out which one to use by following their docs. TL;DR: Navigate to
<JIRA_BASE_URL>/rest/api/latest/project/{project-key}, wherein the project key is something such asINFRAorPOPS. This returns a JSON object, look for its top-levelidfield. -
Issue Type: 10003 = Story, 10004 = Task. If you want another type, see docs.
-
Summary and Description are self-descriptive. They need to be URL-escaped.
-
customfield_12345is for…well, custom fields. For example, we have a custom field to track which team the work item is assigned to.
Bookmark the URL for quick access from your web browser bookmarks bar3, or perhaps from an app such as RayCast.
-
“Issues” were recently renamed to “Work items”. Do you have an issue with this? ↩︎
-
Google’s Issue Tracker (Buganizer) supports a similar approach. For example, https://goo.gle/cftbug redirects to https://issues.chromium.org/issues/new?component=1456689&title=Chrome%20for%20Testing:%20&noWizard=true&pli=1&template=0 (I created this link back in the CfT days). ↩︎
-
I prefer this option. The bookmark label (name) is
+, very mnemonic. ↩︎