What's an organisation/group?
An organisation is a logical unit which can be shared between multiple user's accounts and contains repositories. GitLab does not have organisations, but instead it has groups. From the Behave Pro perspective, organisations and groups are the exact same thing.
Can not see any organisations/groups during project setup!
This can happen if you have not connected your Jira to your Git provider yet. You will need to contact your Jira administrator so that they can connect your Jira to the Git provider.
If you are using GitLab, you must have at least one GitLab group present. You can only connect repositories that belong to some GitLab group. User's repositories are not permitted.
Some of my organisations/groups are missing during project setup!
This highly depends on which Git provider are you using.
If you are using GitHub or Bitbucket Cloud, the list of organisations you can select depends on which organisation have selected during the authentication process of connecting GitHub or Bitbucket Cloud to Jira. To use more than one organisation, you will have to complete the installation process again for any of the new organisation.
If you are using Bitbucket Server, you (your account) must have access to that organisation in order for you to be able to select it. You must also choose OAuth with impersonation during the setup of Application links. Read more here.
If you are using GitLab, this depends on who has completed the initial connection from Jira to GitLab. Behave Pro will be only able to access repositories under the GitLab user you are logged-in during the initial setup. It is highly recommended that you create a machine user for this connection and give that user access to the repositories you want Behave Pro to have access to.
I can not see any git repository during project setup!
Make sure that the organisation/group you have selected contains at least one repository.
In the case of GitHub, you may need to the access, read more here.
If you are using Bitbucket Server, you (your account) must have access to that repository in order for you to be able to select it.
If you are using GitLab, this depends on who has completed the initial connection from Jira to GitLab. Behave Pro will be only able to access repositories under the GitLab user you are logged-in during the initial setup. It is highly recommended that you create a machine user for this connection and give that user access to the repositories you want Behave Pro to have access to.
I can not see any branches during project setup!
Your repository that you are connecting to must have at least one branch. The repository can not be empty. Behave Pro can not connect to that repository if it is empty.
Which Git branch strategy should I choose?