Create multiple Epics from inside Confluence - How to provide Epic Name?

[Christoph E.]

Hi folks, 

I am trying to create multiple issues of type Epic from a cloud instance of Confluence. 

How can I provide the Epic name from a column in the table?

The dialog shows me an input option but since I create multiple epics from a table they end up having the same name. I tried to name the table column "Epic Name" but that still doesn't convince Confluence to give me a drop down selection in the dialog. 

[Darryl Lee]

Community is showing me this related question:

Confluence の Jiraマクロで、Next Gen. の Epic Nameを出力したい。

Which Google Translates to:

I want to output the Epic Name of Next Gen. In the Jira macro of Confluence.

Anyways, it's actually about Jira Macros, but there is a suggestion of using a Parent field. I wonder if that might work as a Column name?

[Christoph E.]

Hi Darryl, 

Could you elaborate the parent field approach a  bit further? 

I am wondering if this isn't about displaying the Epic name, rather using a column derived value when creating multiple epics?

Thanks,

[Darryl Lee]

Yes, the ticket was about displaying the Epic Name, but I thought I would give it a try. No luck though:

Back in 2018 it was rumored that there was a feature request for this:

https://community.atlassian.com/t5/Jira-questions/How-do-you-populate-multiple-fields-in-Jira-when-creating-issues/qaq-p/914524

[Darryl Lee]

Ah, found a few requests to allow setting assignee, which is a similar thing:

https://jira.atlassian.com/browse/CONFCLOUD-44292

https://jira.atlassian.com/browse/CONFCLOUD-34024

Unfortunately neither of those are resolved, and the workaround mentioned, Jcreate is Server/DC only.

[Christoph E.]

I thought already this is probably the case. I was just wondering since Epic is a Jira native issue type that has Epic Name as a mandatory field that this might have been considered. Guess the internal Confluence and Jira team aren't in sync on this, as this behavior renders this functionality useless. 

Fingers crosses one of the above requests makes it on the roadmap!  🤞

Thanks for looking into this Darryl and your help!