Impact of next-gen projects on the Jira Cloud REST API/Marketplace Apps

Jira Development Jira Cloud
, , ,
2

Hi @paulo.alves,

Thanks for posting this in the community. I’ll tap Atlassian who would be better at answering this.

For completeness and for other developers to benefit with this information as well, let me share my response to you:

Hi Paulo Alves,

Here’s what I’ve gathered:

(DW/simplified/agility/next-gen) projects we have 4 projects roles created by default for each new project

  1. Administrator
  2. Member
  3. Viewer
  4. atlassian-addons-project-access

These project roles are scoped only to this new project (cannot be used outside of this project), we have rolled a fix for retrieving the correct project roles for a given project under
/rest/api/2/project/<projectIdOrKey>/role
/rest/api/2/project/<projectIdOrKey>/roledetails

For retrieving all project roles /rest/api/2/role changes are in flight for all rest APIs that returns all things (as statuses, issuetypes, project roles) to include information about these project roles and where they can be use.

In the mean time there are some APIs broken, the team is aware of the issue and there’s planned changes to update the APIs and communicate the changes to developers using these APIs.

More information can be found in: Jira Cloud next-gen projects and Connect apps

Cheers,
Anne Calantog

2 Likes