Can I create Jira issues (mostly tasks) directly from Confluence?

Question

Hi,

I've been using Confluence's inbuilt task list system. It's not bad, but quite limited in terms of management, as tasks are either open or closed. Is there a way to create Jira tasks on the fly (no clicks, just parsing, like with Confluence's tasks) from a Confluence page?

Ideally, I'd like to pass the following: Jira project (could be a default), type of issue (maybe), assignee, due date, title, short description. The goal is really to just type my meeting minutes and be done with it, while still having proper task tracking.

I've googled as much as I could but didn't have any luck finding anything...

Thanks!

Romain

Romain B · Answer

Hi Danny,

Thanks for the answers.

I'll try reaching out to them.

Regards,

Romain

Danny_qtq7b3 · Answer

Thanks @Romain B

Unfortunately I could not find an exact solution to your requirements, instead I think reaching out to Adaptavist regarding their Confluence Scriptrunner add-on may get you one step closer.

The closest example I could find was utilising Adaptavist and Comala Workflows to create jira issues on page approvals. Does not work for on-the-fly Jira Issue creation.
https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Create-Jira-issues-from-inside-Confluence-with-Comala-Workflows/ba-p/1182067

While the end result is not exactly what you require I would suggest reaching out to Adaptavist to see if it is possible to create Jira issues based on a particular Confluence page event trigger.

Apologies I could not be any further assistance,

Danny

Romain B · Answer

Hi @Danny ,

Yep, it's still an issue for me. The use of the Jira macro is too slow for me as it requires many clicks.

My primary requirement is indeed to create issues (tasks) on-the-fly, just as can be done Confluence's tasks. It's lightning fast, and just so efficient... Yet, the follow-up on these tasks is just too limited for me on Confluence, as the Confluence tasks basically just allow you to click when it's done.

Thanks for asking for these clarifications.

Regards,

Romain