nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A way to pre-populate fields on the "Create Issue" page?

I'm using this as a guide:

https://confluence.atlassian.com/jirakb/creating-issues-via-direct-html-links-159474.html

But can not get the customfield_XXXXX to work; the resulting "Epic Link" field on the page always remains blank.

I've examined the source of my HTML, and found XXXXX to be 10008, so I'm using the following:

/CreateIssue.jspa?pid=10000&issuetype=10001&customfield_10008=<value from my drop down>

The first two values are pre-populating the page fine, but the Epic Link field still remains unselected. Perhaps I'm using the wrong 'value'? How do I know what to use for this value?

Accepted answers

All comments

Boris Berenberg - Atlas Authority

I would manually set the value on a ticket, then look at the change history and pull the ID from there.

Thanks for the reply! Working on that now.

I went to a couple tickets which had this in their change history, and found a couple IDs:

SIO-7 [ 10006 ]

SIO-4 [ 10003 ]

And tried modifying my post:

&customfield_10008=10006

&customfield_10008=10003

But neither caused the page to auto-populate those values. Instead, I still have an empty value in the Epic Link field.

Boris Berenberg - Atlas Authority

The format is "key:WBD-1"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software