JIRA Software and branching

Cow Hills October 23, 2018

Hello all,

Currently we are trying to replace our own internal Development issue tracker for JIRA software. Only we have a special why our branching , release and version works.

let me first explain how we work.

we have a Master branch we call the trunk.
in this trunk we do all the bug fixes and development that is done in the underlying branches.

Each customer has his own branch that we do only bug fixes in. and twice a year the customers get a new branch based from the current trunk.

Customer A has branch 1.12 and Customer B has branch 1.13 then the trunk will be 1.14
So als the fixed done in branch 1.12 and 1.13 are also done in 1.14 but only the new development is done in 1.14.

Now Customer A gets the new branch so Customer A has nog 1.14 and the trunk is 1.15.

for each build we run this is a new version but not all new version are released to en customer.

Is it possible in JIRA software do this way of working?

We tough about creating a project for each branch but wit our growing customers base hat will be a lot of projects (30+). so we would like to only use different projects for different products we create for our customers.

We only use JIRA Softeware , Core and Service Desk and use SubVersion for our repository and TeamCity for building it. 

 

0 answers

Suggest an answer

Log in or Sign up to answer