nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Disbale all user connection for upgrading

Mohamed Saad Taha

Dears,

Iam planning for the upgrade so I am asking if i can disable all user access till I finish the upgrade not to do any changes

Accepted answers

Robert DaSilva_a432as

Hi @Mohamed Saad Taha

Ultimately, you have four main ways to accomplish this:

Replace all permission schemes with one that only provides Read Only access
1. Capture a list of all projects and their associated Permission Schemes
2. Create a new "Read Only" permission scheme which provides only the Browse Projects permission
3. Assign this new Read Only permission scheme to all projects
4. After the upgrade, replace the original permission schemes
Block network access through your firewall / load balancer / DNS
1. Ensure that you as an admin have the direct access link, so you can perform the actions you require
Remove all users from the Product Access groups
1. Create a new local group for "Limited Access Only", and add any administrators or users that need to retain access during downtime
2. Add this "Limited Access Only" group to Product Access via the Application Access screens
3. Record the default group that is assigned Product Access
4. Remove the default group assigned Product Access
5. After the upgrade is complete, re-add the default group back to Product Access.
Perform the upgrade during a downtime window (over the weekend or holiday)
1. While not fool proof, it's a good way to ensure most of your users are offline and not adding or updating tickets.

I would recommend option 2 here, where access is blocked at the network level. This should be the most simple change to revert, and should be the most comprehensive in terms of blocking access. You will need to investigate your specific networking configuration to ensure you can make the changes.

Hope that helps!

EDIT: Updated Option 3 to reflect Atalssian's recommendation and documented pathway found here:

https://confluence.atlassian.com/jirakb/how-to-bulk-remove-user-access-from-jira-during-maintenance-or-for-test-instances-1207188639.html

All comments

Robert DaSilva_a432as

Hi @Mohamed Saad Taha

Ultimately, you have four main ways to accomplish this:

Replace all permission schemes with one that only provides Read Only access
1. Capture a list of all projects and their associated Permission Schemes
2. Create a new "Read Only" permission scheme which provides only the Browse Projects permission
3. Assign this new Read Only permission scheme to all projects
4. After the upgrade, replace the original permission schemes
Block network access through your firewall / load balancer / DNS
1. Ensure that you as an admin have the direct access link, so you can perform the actions you require
Remove all users from the Product Access groups
1. Create a new local group for "Limited Access Only", and add any administrators or users that need to retain access during downtime
2. Add this "Limited Access Only" group to Product Access via the Application Access screens
3. Record the default group that is assigned Product Access
4. Remove the default group assigned Product Access
5. After the upgrade is complete, re-add the default group back to Product Access.
Perform the upgrade during a downtime window (over the weekend or holiday)
1. While not fool proof, it's a good way to ensure most of your users are offline and not adding or updating tickets.

Hope that helps!

EDIT: Updated Option 3 to reflect Atalssian's recommendation and documented pathway found here:

https://confluence.atlassian.com/jirakb/how-to-bulk-remove-user-access-from-jira-during-maintenance-or-for-test-instances-1207188639.html

Mohamed Saad Taha

HI @Robert DaSilva ,

thanks, a lot for your reply i though i will be simpler than that and Atlassian provide OOB feature for this activity.

but your answer is very clear appreciated

Robert DaSilva_a432as

@Mohamed Saad Taha It seems Option 3 here can be more easily done through removing a specific group from the product access pages.

Please review Atlassian's recommendation here: https://confluence.atlassian.com/jirakb/how-to-bulk-remove-user-access-from-jira-during-maintenance-or-for-test-instances-1207188639.html

Essentially, you create a new "Limited Access" user group with only your admin account (and any other users you need to be able to access the instance during downtime,) and add that to Product Access. Then, make a note of the default user group assigned product access and remove that. Once the migration is complete, you can add back the primary user group.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

data-center

jira-service-management

jira-service-management-data-center