Integrating Stash with Jira

Our current environment includes Jira, Bamboo, Fisheye, and Crucible. The setup with our existing Atlassian tools is rather simple. Every application that we develop has its own Jira project. Actually, our rule is that every piece of software on its own release schedule must have its own Jira project. Each Jira project maps to one bamboo project, one crucible project, and one fisheye repository (currently using subversion).

Note: We also use Jira for authentication in all of our Atlassian tools.

We are now adding Stash in order to migrate from subversion to Git. However, it is not clear if I should be creating one project in Stash for each Jira project. Are there any benefits to having a one to one mapping between Stash and Jira projects? Are there any guidelines for this?

1 answer

0 votes
Timothy Chin Community Champion May 13, 2014

Are there any guidelines for this?

The general answer is that if your repositories are common to each other, you can lump sum it into one project. For example, in a JIRA project, you have 2 components and each component has it's own repository, in Stash, you can create one project and 2 repositories in it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you