When creating an issue via URL, how to add components and labels?

[Tony Chung]

When we were on Jira DC (Server) I had a handful of links that I used to create issues in different projects, and added components and labels automatically as list items. With Jira cloud, I can only create an issue in a project and define its type, but I can't add components and labels.

For example, to create an issue of a specific type in a specific project, this opens the form field:

> https://myjira.atlassian.net/secure/CreateIssue.jspa?pid=10008&issuetype=10068

However, I used to be able to add components and labels (and populate custom fields):

> https://myjira.atlassian.net/secure/CreateIssue.jspa?pid=10008&issuetype=10068&components=["Comp 1","Comp 2"]&labels=["label-1","label-2"]

But in Jira cloud this feature doesn't work anymore (edit to add) as it did on Jira server.

Also, can someone share the official documentation for creating Jira Cloud issues via URL and all the parameters and usage syntax?

[Bill Sheboy]

Hi @Tony Chung 

For Jira Cloud, please see this documentation for creating an issue with the REST API, including the details of adding components and labels to it:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post

Kind regards,
Bill

[Tony Chung]

Thanks @Bill Sheboy but that's not what I asked. I am asking for using the URL method because that works best for creating issues from Confluence (rather than needing to call separate script just to create issues).

I figured that since this functionality existed PRE-cloud, it would be nice to learn how to use it POST-cloud.

[Bill Sheboy]

To clarify, I do not believe it's possible to create an issue in Jira Cloud with only a URL. ..but I certainly could be wrong, so perhaps someone else will comment with more info.

The closest match to that I can think of is the issue collector, which leads to a feedback page to create issues: https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/

You noted earlier:

But in Jira cloud this feature doesn't work anymore.

Did you observe this working at some point in the past with Jira Cloud, or are you noting this difference from the Server / Data Center version?

If you are trying to create issues directly from Confluence, based on some user activity, perhaps investigate the features of Confluence automation rules to do this.

[Tony Chung]

Thanks for helping me clarify. In Jira cloud this feature doesn't work, like it did with Jira server. I'm not sure I understand why this would have been disabled. Or maybe I capitalized on a little-known feature of Jira server that wasn't supposed to work?

[Bill Sheboy]

Your last point seems to be the case: there are lots of things people have discovered over the years with Jira which are unsupported / internal functions or which have been deprecated.  (e.g., there were REST API functions with the old Greenhopper features to return the data and chart for the sprint report and those seem to be deprecated.)

You are on a paid Jira license, so I recommend working with your site admin to submit a support ticket to ask the Atlassian team.  Perhaps there is a supported method to do what you ask which is not well-documented.  You can do that here: https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thanks!

[Tony Chung]

Thanks @Bill Sheboy !