Today I am unable to edit the Release date on a /projects/{projectname}/versions/ Release page. When I try, the error message that I see is:
"We couldn't update the release date. Something went wrong. Please try again or contact your administrator if the problem persists."
I am an Administrator in my software project and have also (after this happened) found this document https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/#Manage-Versions , so then I added the Administrator role to the new "Manage Versions (Releases)" permission in my project settings. And according to Permission helper, I have all the needed permissions.
The only thing that changed before I encountered the issue was that we started a Jira Service Management trial on our Jira cloud site, and I started a new service managed project. I was unprepared for how (badly) that project worked however, and after struggling with it for a while, I realizing that I could move tasks into it but not out of it (because Jira Service Management will override a bunch of permissions in the new project when you're using the trial). So I deleted the project, and we've cancelled our trial.
But it still appears to have affected my permissions in my original Software project.
At least via correlation, this seems related to https://jira.atlassian.com/browse/JRACLOUD-94667 and perhaps also to https://jira.atlassian.com/browse/JRACLOUD-97139
Hey @Clare Averill ,
As you've already checked, it seems you have all the necessary permissions 👀
You could try 're-updating' permission schemes with the same roles to the mentioned permissions, just to be sure.
I'd probably suggest reaching out to Atlassian Support in this case, as they can check if there's a backend issue causing the experience you're having. 👈
Apart from that, there are some official articles related to JSM permissions and troubleshooting:
But these are all related to JSM and not Jira (software or business) spaces.
Cheers,
Tobi
hi Tobi,
Today (Monday) the issue has resolved itself after being visible Thurs and Fri of last week. Allowing extra time to pass was apparently needed (more than overnight).
Thanks for your help though! I'll reach out to support if something like this occurs again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.