Our CI/CD pipelines are critically impacted due to unexpected changes in Jira Cloud default project permissions.
Without any modifications on our side (to either user permissions or project permissions etc), projects created by our automated tests suddenly no longer allow users (including site admins and project leads) to delete issues. This has broken all of our automated test setup/cleanup processes and is blocking delivery pipelines across multiple instances. We are suddenly seeing the error for every instance:
Request to Jira failed with status 403: You do not have permission to delete issues in this project.
We create projects using the following template via the REST API (${baseUrl}/rest/api/2/project):
com.pyxis.greenhopper.jira:gh-simplified-basic
It would be great to know if other users are experiencing this issue as well? I have raised multiple support tickets with Atlassian and the responses so far have claimed there have been no changes to the default project templates/permission schemes.
Recently, we have observed two major issues with this template:
-
Permission changes – Projects created from this template no longer allow issue deletion, even for site admins.
-
Issue type changes – The Story issue type appears to have potentially been removed from the project template as well.
Correction after further investigation:
- This is happening to Standard Jira instances
- Custom project permission schemes are being revoked from the instances
- New default permission schemes are replacing the revoked permission schemes
- Newly created projects are being assigned the new default permission schemes
- The new default permission schemes are more restrictive than the default schemes we had in place before the change, which is breaking our automated tests
- The only way to fix this to unblock the pipelines is to wait for the new change to be rolled out to the instances, then update the new default permission scheme manually in each individual instance
These changes occurred without any configuration changes on our side and without any documented communication (that we have found after checking blogs and changelogs and announcements) from Atlassian, unless we are missing a communication.
Can Atlassian confirm:
-
Have there been intentional recent changes to the default permission schemes or to the behaviour of this project template?
-
Where can we find official release notes or communications describing these changes?
-
If this is the new expected behaviour, can you recommend an alternative project template that:
-
Supports Epics
-
Allows issues (including Epics) to be deleted by project administrators or site admins
-
This undocumented behaviour change is proving highly disruptive and is costing us significant time to investigate. If Atlassian intends to modify core project templates this dramatically (removing permissions and issue types), there should be clear announcements and warnings to avoid breaking customer pipelines and ongoing work.
We would appreciate urgent guidance to unblock our delivery pipelines.
We are obviously able to go into each test instance and manually update permission schemes, but this could take a while as we have a lot of test instances.