Hi Team,
I need to set up the GitHub for Jira app provided by Atlassian for Offcial. I have a couple of questions regarding this setup.
First, I have Jira admin access, but I do not have access to GitHub since it is managed by a different team. Is it possible to complete part of the installation from the Jira side and then have the GitHub admin handle the authorization on their end? Is there a way to share a link or trigger the authorization process for them?
Second, during installation, the app requests read and write access to repositories. Suppose a Jira user does not have direct access to a specific GitHub repository, but due to the write permissions granted by the app, they are still able to create a feature branch from Jira. How can this be restricted? The repository is private. Currently, I am using a GitHub organization trial, but the final implementation will be on GitHub Enterprise Cloud.
Thank you in advance.
Dvipa
Hi @kshridvipa7878 ,
It kinda depends how you're connecting these two. Assuming we're talking about native integration, one of the first steps is to perform authorization > meaning, that would need to be done by GitHub admin.
Although... after reading the linked docs, it seems you don't necessarily need to be a GitHub admin and you can just share the request link:
If you don’t have the Connect button, you’ll need to request a GitHub organization owner to connect the organization for you.
Select Send them a link and ask them to connect.
Copy the message and URL from the Send a link to an organization owner dialog that opens and send them to the GitHub organization owner for approval.
All the connections we did were with admin account so I might have missed this 👀
As for the second part, once you create the connection, you can configure the part/permission when it comes to creating branches from Jira > read more here: Create a branch in GitHub based on user permissions
Again, this all relies on the fact that we're talking about native integration. If you're using a Marketplace app/solution, then I'd recommend reaching out to their product/dev team directly.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.