I have a few questions coming from the perspective of a Jira Cloud admin.
Does the Jira Cloud admins have to update the all the permission schemes manually or the updates will be done automatically with a tool? This is a challenge for sites with a lot of permission schemes. It is an administrative nightmare to get inputs from project owners to decide on the new permissions.
Is the Permission Helper going to be updated for this?
Is Jira Cloud Migration Assistant (JCMA) going to be updated for this? Will it affect the migration of Server instance to Cloud?
Thinking aloud, will it be easier to retain BROWSE_PROJECTS permission as it is and introduce VIEW_PROJECTS as a new permission? This permission can be granted to allow users who does not have BROWSE permission but need to view the projects.
I will check with my dev team and get back to you soon.
Meanwhile, we have rolled this out to the EAP cohort as mentioned in the post. In case you are part of that, I would request you to try out these scenarios.
Hi, Thank you for the questions
- The updates will be done automatically. So admins for sites with lots of permissions don’t have to worry about it.
- Yes, Permission helper will be updated for this
- I will check it and get back to you soon. As of today, we believe it won’t impact the JCMA, but I’ll still make sure and reply back.
- We had considered that as an option, although we wanted to avoid confusion by not keeping 2 permissions that behave similarly. I will keep you posted if there are any updates on this.
As a Jira admin and vendor i had the same thought as huasoon that leave browse projects as is and just add the new view projects privilege.
Much smaller change and non breaking. Also prevents need to check 2 separate privs because (to me) the browse project/view issue implies the user can see the project.
Is there a use case where a user would need view issue and NOT view project?
My 2 cents
Today, Sept’23 I’ve tried:
https://<mysite>.atlassian.net/rest/api/3/permissions - no VIEW_ISSUES permission.
https://<mysite>.atlassian.net/rest/api/3/mypermissions?permissions=VIEW_ISSUES - error “VIEW_ISSUES”: “Unrecognized permission”
Is the stage 1 postponed?
I guess Sept’22 meant somewhere in September 2022, not 22th of September. Just saying.
@stefan_hc @VaradPingale Aha I am sorry, my misunderstanding, so I’ll wait till October’22.
Thanks for checking in, and apologies for the delay in replying.
As @stefan_hc mentioned, we were planning to release this to everyone by September 2022.
We are still evaluating these changes based on some of the feedback we have received in the comments, hence it might take one more week to get back on when we can release this to everyone.
In the meanwhile, I would request you to enroll a test instance in the EAP cohort here Jira Cloud Vendor First Release if you want to try out the change.
Thanks for the feedback. We are evaluating this approach before we rollout the change to everyone.
Will keep you posted on this.
Update on above announcement:
On Aug 19, 2022, we announced the “Introduction of two new permissions to replace Browse Project permission”. It was planned to be released by end of September 2022.
We’ve since received feedback from many of you on this being a fundamental change in how permissions work, and the requirement of more notice period to adjust with the change. As a result, we have decided to NOT rollout this change to any of our customers till 31st March’23.
This means, Browse projects permission will continue to work as it is, and the two new permissions won’t be introduced till then.
Meanwhile, our team will evaluate the different cases mentioned in the comments to ensure all of them are addressed.
In case you are interested in trying out the change, please enroll yourself in the EAP cohort Jira Cloud Vendor First Release. After getting adequate feedback from this cohort, we will inform you well in advance about the revised timeline of the rollout of this change.
Thank you for your feedback and apologies for any confusion caused by the earlier announcement or this revision of the timeline.
Thank you for being an Atlassian partner. If you have any questions, please drop them in the comments section. We will keep you posted.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
After the rollout on 31st March’23 both Browse project permission and the two new permissions will continue working together until 6 months later?
Any update on when the old Permission will be removed, or is this something that will be updated after 31st March '23, when both sets of Permissions are rolled out?
@VaradPingale @ibuchanan - where does this stand now? March 31st is approaching soon and it is completely unclear to me what, if anything, will happen. I suppose that the content that is “outdated as of Oct 22” can be disregarded? Please help us understand what’s going on, this is having massive impact on pretty much any Marketplace app.
@VaradPingale are there any news regarding the rollout, and what exactly will happen on March 31st?
I’m assuming the initial plan (stage 1 and stage 2, with at least 6 months in between) is still relevant, but it would be good to have a confirmation.
Is it possible to know what is the current situation of this?
It is almost 31st March and we have no news.
Update on above announcement:
We had earlier announced that “Introduction of two new permissions to replace Browse Project permission” was planned for release on 31st March ’23. Since then, we have received questions regarding the rollout from our partners and customers, which we are still in the process of addressing. As a result, we have decided to NOT rollout this change on 31st March ’23 for Jira Cloud.
This means, Browse projects permission will continue to work as it is, and the two new permissions won’t be introduced until further notice.
Meanwhile, this work is still a priority for us, and our team is evaluating all the questions and concerns mentioned in the comments. This process of evaluation will take a few more weeks. Following the evaluation, we will inform you about the revised timeline for rollout, well in advance.
In case you are interested in trying out the change, please enrol yourself in Developer Canary Program
If you have any questions, please drop them in the comments section. Please expect more communications on this in upcoming few weeks.
Thank you for the update!
Hello, is there any update on the evaluation process and when this change will be rolled out?