Can't create Jira issues of type Epic

[Gannon_Hall1]

I can’t create a Jira issue of type “Epic”. I get an error each time. Changing the issue type to Task or Story works fine. Any ideas?

[MairaStorch]

I’d like to create Epics from Coda, too

Still generates an error…

[Jean_Pierre_Traets]

Dear @Gannon_Hall1,

Better now then never, this might be what you have been looking for:

Get Jira issue ID from issue created with the Jira pack create button

Hi Maira, Welcome to the Coda Community! If you have a “Create Issue” button in a table, you can add an option to it for a results column. I name mine “Results”. That will return the Jira ID and associated data… Since we don’t return the full JSON data anymore, the following won’t work. You can make this result column a Jira Issue Column Type and it will sync in the issue information that you can then pull from to get any extra data you might need. [image] This is the return value that Cod…

[BenLee]

This might be an issue with Jira’s different types of projects. I’m not sure if our pack can use epics if it’s a “Classic” project. I think the “Next-gen” projects should work for an epic.

How can I tell whether I'm in a classic or next-gen project? | Jira Service...

I’ll try to test this out and see if this is the issue.

[Gannon_Hall2]

Support for “Epics” broke with the new version of Jira. The version that looks like this.

[BenLee]

I checked with engineering and it’s a known issue and currently we don’t have a solution. It’s in our notes and we’ll check it out and see if we can get it up and running.

[Pearson_Henri]

Same thing. This would be great!

[Gannon_Hall1]

Any news on this bug? I’m doing a manual workaround still. Solid support for the Jira object model t (Epics, etc,) would be awesome.

[Gannon_Hall3]

FYI that the workaround for this is to use Zapier as it supports the creation of Epics for “classic” projects in Jira.