Permission Scheme changes moving to Cloud

[Mykenna Cepek]

I'm supporting my org moving from Jira Data Center to Jira Cloud. (and yes, we have a vendor migration partner).

I've compared the permissions managed by Permission Schemes, and there are differences between Data Center and Cloud. I have questions...

1. The "Browse Project Archive" permission is not in Cloud. How is that managed?
2. The "Edit Sprints" permission is not in Cloud. Does the existing "Manage Sprints" permission now include this?
3. "Start/Complete Sprints" permission is not in Cloud, but it seems to be covered by "Manage Sprints" as documented here.
4. The "Log Work for Others" permission is not in Cloud. Does the existing "Edit All Worklogs" permission now cover that? *
5. The "View All Worklogs" permission is not in Cloud. How is that managed? *
6. The "Impersonate users in A4J project scope" permission is not in Cloud. Seems like this is allowed for Jira Automation rules in the Cloud by default now (based on this documentation) - yes?

The two marked with * might relate to the Tempo Timesheets and/or Planning apps that we had in our Jira Data Center. Since we're not retaining those in the cloud, maybe those are moot?

We have a custom Permission Scheme we use for all projects, and I want to ensure we recreate that faithfully in Jira Cloud. Understanding the differences outlined above will help in that quest. Thanks!

[Aaron Geister_Sentify · Accepted solution]

@Mykenna Cepek

Let me see if I can help answer a few of these questions for you. 

1. The "Browse Project Archive" permission is not in Cloud. How is that managed? There is a new archive permission which would allow for this. It's not live on all sites yet and still in beta but would be the answer to this question.
2. The "Edit Sprints" and "Start/Complete Sprints" permissions are not in Cloud. Does the existing "Manage Sprints" permission now cover those two permissions also? If so, some fine-grained control seems to have been lost. In cloud you would need manage sprint permission and schedule issue permission
3. The "Log Work for Others" permission is not in Cloud. Does the existing "Edit All Worklogs" permission now cover that? * This is to use the Edit all, so you are correct.
4. The "View All Worklogs" permission is not in Cloud. How is that managed? * View All Worklogs is available in Cloud
5. The "Impersonate users in A4J project scope" permission is not in Cloud. Seems like this is allowed for Jira Automation rules in the Cloud by default now (based on this documentation) - yes? Yes, you can set the users as any users to run on behave or you can use automation for Jira as a user. This does allow this because of the atlassian-add-on.
   
   When you are migrating, these permission schemes should be able to map to the new permission in cloud to facilitate the difference. 

[Mykenna Cepek]

Thanks, @Aaron Geister_Sentify

Your #4 answer confuses me though. I'm looking at the Default Software Scheme in a trial Jira Cloud project. I search the page for "worklog" and only find these:

• Delete All Worklogs
• Delete Own Worklogs
• Edit All Worklogs
• Edit Own Worklogs

I do not see "View All Worklogs" in the Permission Scheme. Do you actually see it in your Jira Cloud?

[Mykenna Cepek]

I'm also concerned that we might be miscommunicating about #1. I'm aware there is a new Archive Issue feature recently release for Jira Cloud. But that's not what the "Browse Project Archive" permission relates to in Jira Data Center.

As I'm sure you know, archiving Issues and archiving Projects are two different things. The permission I identified in my #1 relates to the latter (project archiving).

The new permission scheme features you allude to appear be related to the former (issue archiving).

So I'm still wondering how Jira Cloud controls access to Browse Archived Projects? 

[Aaron Geister_Sentify]

@Mykenna Cepek 

I do see view all worklogs in my permission schemes in cloud.

[Marc - Devoteam · Accepted solution]

Hi @Mykenna Cepek 

@Aaron Geister_Sentify is right on the topics.

The questions you still have I will try to answer.

On the archiving option, Yes you can archive projects, but you are not able to browse them while archived.

User by default have permission to view all work logs, there is no separation in this. This is based on granting browse permission.

[Shah_ Piyush]

Regarding...

This question: 

• The "Edit Sprints" and "Start/Complete Sprints" permissions are not in Cloud. Does the existing "Manage Sprints" permission now cover those two permissions also? If so, some fine-grained control seems to have been lost. 

And this answer:

• In cloud you would need manage sprint permission and schedule issue permission

My further question ....

The description of Schedule Issues --> Ability to view or edit an issue's due date.

How does this description map to "Schedule Sprints" which we now no longer have in cloud?

It does seem to me that edit, manage, schedule sprints is now all part of manage sprints in cloud.  I like this simplification, but I am sure someone has a real valid business case to separate the three.

[Gökçe Karaduman-The Starware]

Hi  @Mykenna Cepek ,

Yes, you are right, the worklog related permissions are probably added by Tempo or another Timesheet app. If you want these in the cloud, you need to use a timesheet app, like WorklogPRO. The cloud version of WorklogPRO provides "view all worklogs", "view own worklogs" and "log work for others" project permissions.

Disclamir: I am the employee of the vendor who developed this application.