REST API for new Jira Projects

Description

The new jira projects allow users to create project scoped entities like IssueTypes, Custom Fields and Statuses. However there is no public API for connect apps to create and update project scoped entities. Additionally the existing APIs return both global and project scoped entities.

For additional information please refer to the following blog posts

https://community.developer.atlassian.com/t/jira-cloud-next-gen-projects-and-connect-apps/23681

https://developer.atlassian.com/blog/2018/10/next-gen-projects-jira-cloud/

Environment

None

Activity

Show:
Oleh Motnyk
November 12, 2019, 7:50 AM

Sounds great!
Can you provide us with at least very rough estimate? For example, it should be ready until the end of this year or the end of the Q2 of the next one, etc. I just want to understand the priority of this issues/project and see when we should come back to this and start thinking about supporting Next Gens.

Stephanie Seymour
February 5, 2020, 3:18 AM

One of our Marketplace apps integrates with existing Jira issues using custom fields. It creates and manages it just fine for users in Classic projects but we’re looking to make it compatible with Next-gen Projects as well.

We’d need to be able to create custom fields in Next-gen Projects so that users can add these relevant fields to their Issue View and to their issues.

Is a custom field API planned for 2020?

Abhinaya Sinha
February 5, 2020, 12:48 PM

Hi and thank you for your engagement on next-gen APIs.

We are working on building the ability to create custom fields in next-gen projects. Once built, you’ll be able to create custom fields via connect modules and REST APIs. We’ll enhance the existing connect module to also work for next-gen. And build a new REST API that will be project-scoped.

We are targeting to have one or both of these ready by June 2020.

Abhinaya Sinha
April 5, 2020, 7:02 AM

Hi and More details to my earlier email - we are working on extending support for app custom fields. To start with, we'll be making sure the existing issue field module can work for next-gen. That way, developers/vendors such as yourself, wouldn't have to change anything to make your code work for next-gen. In a similar vein, you'll continue to use existing issue field options REST APIs to provide values for those custom fields.

How do you add/create these app custom fields when you do so for the first time? Do you use the issue field module? Which apps do you have on the marketplace? And would us supporting custom fields suffice to get those apps to work for next-gen?



Stephanie Seymour
April 6, 2020, 1:21 AM

Hi Abhinaya,

Yes, we use the issue field module already for custom fields in Classic Jira projects. We'd love if the existing APIs worked for next-gen.

I work for Easy Agile - the app I've been working on that utilises custom fields is Easy Agile Personas. If existing issue field options REST APIs work to let us create and update custom fields, the app would be able to work the same on next-gen projects as it does on classic projects.

Another app of ours, Easy Agile Programs, is using read-only custom fields on Jira Server. When we develop this feature for Jira Cloud and next-gen customers, the app will need to use the issue field module as well.

Assignee

Unassigned

Reporter

Mythili Gopalakrishnan

Labels

Components

Affects versions

Epic Name

API Support for Next-Gen Projects
Configure