It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Create Issue dialog - preselect pid & issueType

I would like to construct a URL that if clicked lands me on:

I know how to pre-select the Project ID (selectedProjectId=10603):!default.jspa?selectedProjectId=10603

what parameter should I use to pre-select the issueType ID along with PID?

5 answers

1 accepted

4 votes
Answer accepted

the correct URL for the above screenshot:!default.jspa?selectedProjectId=10603&issuetype=3

That does the trick! There is some way of getting the just created issue's id?

Had to replace selectedProjectId= with pid= in JIRA 6.4.9


Recently, I've found another way to open the create issue/subtask dialog. Here it is:

// Create Subtask
  .createSubtaskForm({parentIssueId: 10110})
  .asDialog({windowTitle: 'Create Subtask'})
// Create Issue
  .createCreateIssueForm({pid: 10000})
  .asDialog({windowTitle: 'Create Issue'})

Now I don't have to create hidden links to open them anymore.

Like Randall A. Gordon likes this

How I can set the parent iD in as a parameter URL? 

I tried

But it dosn't work


I don't believe this is possible. You have to open it using javascript.

Is using JIRA.Forms still up to date or should i use AJS.Dialog instead? or is that something different?

using parentId makes sense when you are creating subtasks via html links. And the correct syntax would be as per below:


You can look on the project page. On the summary page there are buttons for the first issue types with the correct links for it. E.g. you have to use


oh, right... thanks! - how could I forget that?

this works, although I am still curious if there is a way to preselect both PID and IssueType for the view in my screenshot

Hi, is there a way of not getting the huge ERROR sign saying: "You are not logged in, and do not have the permissions required to create an issue in this project as a guest. To create an issue first log in" That is quite annoying for a user that has never used JIRA before. Does not look very professional. I would like to get to the login screen immediately.

Yes, you need to login to JIRA before you access the create links or you can login directly from the create link. This is because JIRA needs to authorise that you are JIRA user before you can create a JIRA issue.

If found something even better :-) You can use this

&lt;div id="create-issue"&gt;
&lt;a href="/secure/CreateIssue.jspa?pid=10603&amp;amp;issuetype=15" class="create-issue-type" data-pid="10603" data-issue-type="15"&gt;create issue&lt;/a&gt;

to open a popup Create Issue screen if your JIRA version supports this. The data-... parameter must match the ids of the link (in fact, the link isn't even used if the popup could be opened).

Because of the needed surrounding element with id "create-issue" there will be some CSS formating applied to the link, which maybe you want to manually remove by applying some style parameter.


Ok, this is not a simple URL.... I use this to display a "support" link on every page through the announcment banner and want to share it :-)

Hi Hennings,

How will we get the defect id that is created? or How the parent page will get the Defect id that is created using direct html Link?

Hi Gopi,

I'm sorry but I don't know how to get the issue key of the created issue. Maybe you should ask this as a separate question.


any chance to pass a parameter for a custom field so it will be pre-filled with the passed value?

Like Anthony Sylvester likes this

I just found this link: In spite of this, I was not able to do this some months ago and there is an open issue on Atlassian's ecosystem, with lots of votes, asking for this feature.

thanks. the problem with this is that when you use CreateIssueDetail.jspa and provide the parameters, the system immediatly triggers validation and you end up with an error message. in my case I want to pre-populate some fields and other (mandatory) fields should stay blank.

You got it! That was the problem when I was trying to do the same thing. So, I really don't believe this is possible. I can't find the open issue that I told you :(

I don't know but perhaps the usage of os_destination can solve the problem? See another case at

I am aware of - but this assumes I know about reporter/summary - and throws error msgs if used with just pid and issueType.!init.jspa?pid=10603&issuetype=15

I can not create the link without issuetype



works, but 



does not work. I can not choose an issue type, it will say "No issue type selected".

So you have to have a minimum and can not combine as you like.
Same/similar btw for priority. If I remove that part it chooses Critical, which, for this project, is not available.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

How InVision centralized their tools and scaled their remote team with Atlassian and Slack

Hi Atlassian Community, We recently published a case study that we thought you might be interested in. Learn about how InVision built their fully remote company’s culture using Atlassian and Slack ...

236 views 0 1
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you