Cannot transfer one organisation to another

[Gero]

Hello, I did some mess while setting up my Jira products, and have now 3 different organisations. Would like to get rid of two of them, but as far as I've understood it's incredibly impossible. So I tried transferring both to the only one I'd like to keep, but I keep receiving an error message saying like

The action cannot be performed at this time. Try later.

 Somebody can help me about that? I'm administrator of every organisation, and the only one with a verified domain is the target one.

Here attached an image of what I get; it's in Italian, but you can see the error message at the end.

[Joe Pitt]

As Nic says, you need to remove permission. JIRA works on the grant permission model. There is no deny permission option. Many people put the jira-users group in the permission scheme which gives everyone who can logon whatever permission the group is put in. That route leads to issues like this. That group should only be used if you are absolutely sure you will ALWAYS want everyone to have that permission, which is seldom the case. 

[Vick Ghadimian]

ok, so I created a new group.. how do I configure the settings of my group?

The UI of Jira, or atlassian products in general are not very intuitive.

[Joe Pitt]

You don't configure setting on the group. You configure the PERMISSION SCHEME. As Nic and I said, you need to FIRST remove any group that has logon permissions from the permission scheme. Then add the new group to the permissions you want. This may require having more than one permission scheme. 

I use project roles so I can have just one permission scheme. There may be roles some projects don't use, but I find in the long run it is easier to manage JIRA as a whole. It also allows project leads to add/delete users from the roles instead of needing JIRA admins to add/delete group membership. 

When you created the group did you give it logon rights? If so, any new user created will automatically be put in the group (built in behavior) so you'll soon have more people accessing your project that you don't want to. 

[Katherine Burkholder]

This is all too complicated. Why can't we just have a simple option (checkbox) to hide a project from view when selecting projects from the issues screen? Just have it be visible in the main master projects list, but hide the project and its boards from the issues screens? 

[Sekhar Chandra]

@Joe Pitt 

"When you created the group did you give it logon rights?".

How to do this?

[Nic Brough -Adaptavist-]

You need to remove them from whatever role, group or setting that is granting them "browse project" permission in the permission scheme for that project.