is it possible to create multiple projects but use single SVN repo?

We currently have a JIRA project with KEY "CLP". The project has an associated subversion repo (under /svn/CLP/ in Fisheye). We'd like to create an additional project (say "FOO") but point them at the existing "CLP" subversion repo (such that issues' "Source" tabs would display commits to CLP svn repo if commit log message contained FOO issue key ie. "FOO-100". Is that possible?

Thank you,

7 answers

I had the same problem as dukehoops here, and I am disappointed to see that such a setup is not possible with Jira OnDemand. we have a pretty big product with several parts (UI, CORE, SQL), and we have found it best to have separate projects in JIra for these. But now we'll have to reconsider that setup.

Could you please add this as a feature request for your next product release?

I talked to FishEye support and we're going to try this tomorrow. In the meantime, can you provide your version numbers for JIRA and FishEye? Thanks!

In standalone FishEye and JIRA this is easy to accomplish.
Just add an extra Application Link to the CLP repository in FishEye, pointing to the FOO project in JIRA.
You end up with two Application links from the CLP repo, one to CLP and one to FOO.

However, in an OnDemand instance you don't have this level of control.
When a JIRA project is created, it creates the SVN and FishEye configuration for you.
There's a fixed 1-on-1 relation between teh products, you can't add extra Application Links.
So what you want to accomplish is not possible in OnDemand.

Same problem here.

The rationale behind how we organize code in SVN and how we organize tickets in JIRA are different.

On SVN we do fine grained splits in order to increase code reuse.

On JIRA the point of view is the one of the project manager and the fine SVN structure provides too much detail.

This 1 to 1 mapping doesn't make sense.

132412341234

This is very much an essential feature, anyone with projects bigger than small will absolutely need this. How can we push this up to a feature request? This could be a show stopper for us.

Same here - we are trying VERY hard to move to ondemand for a 20MM line application that is across several projects - but currently a single repo.

With legacy projects - you rarely have a one to one mapping between projects and repo's.

We REALLY need some way for this to work. Can support setup the links for us once we have the projects and repo's created?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Tuesday in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

158 views 3 6
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