At our company we have 10 to 12 difference pieces of software we develop. All of this software will then periodically be combined together into a large installable. Each piece of software has it's own version number system unrelated to the others. We would like to make a JIRA project for the assembly of the installable by a special team. Ideally we would like to be able to choose released versions of the other software form their respective projects when making the ticket so it is all cross-referenced. ie.. Installable 1.0.0 has softwareA 4.3, softwareB 7.2, etc etc. We can do this manually obviously using tickets. But I was wondering if there is a more automatic way anyone can think of?
What I imagine is creating a new ticket for software packaging. And then one would be able to choose from dropdown the released versions of software from other projects. When one would view the ticket you would see what software had gone into it with click backs to their projects.
You could try making an Epic for each installable. It could be modified to basically be a dummy version, as these are the only things that really work cross project in terms of linking things.
For a better answer though, it would be good to know what you use versions for in your system? Are they to track releases to a testing system, are they done using Bamboo?
Also, what is the relationship of feature to release, and release to installable? Is it one feature per release or many to one (or many to many)?
Thanks and good luck!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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