Is it possible to configure OnDemand to be 1 repository per project rather than 1 per account?

Our preference for workflow at the company is to have a single repository per project. Since we often have projects that go dormant for long periods, this keeps the version numbers (that are tied to SVN builds) more consistent to the end user when updates do occur.

Because of this, we usually like to have a single repository per project so commits to a different project will not cause a large jump in the revision of an older project when we go to update it. (IE Project 1 is at rev 3, we make 100 changes to Project 2, now next bug fix to Project 1 puts the rev at 103)

Thank you

1 answer

1 accepted

2 votes

Hi Zachary,

Your use-case makes sense but OnDemand does not support this. There are a number of technical limitations in the way of implementing this, and will not be pursued in favour or working towards better DVCS support.

The feature request is at

Suggest an answer

Log in or Join to answer
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

340 views 0 9
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot