Create JIRA issue from Confluence

[Stephen Hayden]

So I am learning Confluence, is it reasonable to be surprised that I can't construct a form and have it serve as a template to create JIRA issues (or maybe even have Confluence retrieve the relevant create screen for embedding?)

It seems the most efficient ways to create issues from Confluence is to make them click over to a create screen in JIRA via an argument-laden link, or have forms submit emails to JIRA to then pick up?

Seems this functionality has been brought up periodically over the years, but I am just now catching up with the conversation, the above are still the best solutions to creating a JIRA ticket from Confluence?

I am envisioning a single place to go for a project... a Confluence space with a straightforward table of contents containing 'Create Issue' (with embeded form), 'Statuses' (with Jira Issues listed in a page) and then of course a myraid of appropriate documentation. It appears they'll have to leave confluence, or I'll have to fully explore the email approach?

Any input is appreciated, thanks!

[Renjith Pillai · Accepted solution]

Does the Issue Collector plugin help? https://plugins.atlassian.com/583856

[Stephen Hayden]

Has potential for sure, thanks for the tip!

[alexqfredrickson]

This is a dead link.

[Nic Brough -Adaptavist-]

It's six years old.  I think you need to look up issue collectors in Jira's docs

[Yuval Gershfeld]

Hey @Stephen Hayden 

In Methoda, we created an add-on, Jcreate, that allows you to create a Jira Issue from inside confluence while adding many customisable fields.

See: Jcreate | Atlassian Marketplace

[Stephen Hayden]

So Renjith V [NSN]'s answer does help solve the subject, but one of the requirements for my project is that a form is able to be filled out partially and can be come back to later. My understanding was that perhaps I could make a template that would be used for a new page, which would do the above (ideally once complete... submit to JIRA, something that doesn't appear possible). What I am missing is the connection to JIRA for the workflow... hmm, or maybe we just use Ad Hoc Workflows and remove JIRA from the equation? Would love to hear some thoughts along those lines. I guess we'd then be missing all the filters and analytics you can pull from the various data points unless you can do the same in Confluence somehow.