I want to set up a connection between one JIRA project and one Stash repository (perhaps the whole Stash project). Preferably, I would like to make it seem like the other server does not even exist for all the other JIRA projects and Stash projects/repos.
The application links on both sides seem to be global.
How can I restrict JIRA's access to a Stash project or a repository? (And preferably also restrict Stash's access to only one JIRA project.)
JIRA will only show in its tickets the contents you decided to link, i.e. commits from Stash by specifying the JIRA issue key in the commit message, or branches created in a repository from a JIRA ticket, for instance. Could you please clarify in which way you expect this restriction to work, i.e. what actions you are intended to perform for which you would like to restrict what informations are shown?
At first one thing I was able to think about was when creating a branch from JIRA in a Stash repository. In this case I wonder you may only want to have a specific repository/project listed. In this case I think you could control this by playing with Stash permissions, so the user creating this branch from JIRA wouldn't be able to create a branch in a repository for which he doesn't have write permissions:
Please let me know if I am in the right path.
Preferably, I would like to make Stash completely invisible from all other Jira projects. The Jira belongs to our parent company and it hosts projects for many daughter companies. The Stash instance is ours and I do not want anybody else to access it. Also, I would prefer not to give others UI elements hinting to a Stash instance, because it might be misleading. I hope this gives you the idea.
I would also like to figure out how to do this, for different reasons. In our case, I don't want forked repositories to be seen in Jira. Forked repositories will have all of the same issue id's in commits and multiply the commits shown in Jira's development frame. It isn't a matter of just creating branches from Jira, it is a matter of confusion, when there is one blessed repository that we release from and several forks where development of features may take place.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot