Having a Software version with tickets contained in differents projects (sapces)

Question

Hi,

We have several projects (CN, OC, TUR,...).

In this projects we have JIRA tickets (ie : CN-4, OC-154 , ... TUR-42... etc..)

How to create a delivery software version (ie : v1.3) in CN space with OC-154, TUR-42,...) because in OC & TUR spaces We can't find the V1.3 version.

Dick · Answer

Hi @bruno_bobichonwelcome to the Atlassian Community

If you make an Epic in the CN project, it can hold Jira-items from the other two projects:

ie. Epic = CN-123

if team OC does work on this epic in ticket OC-23, they paste the value CN-123 in the parent link field.

Similar to team TUR. Issue TUR-56 can hold value CN-123 in the parent link field as well.

You can then make a release in the CN project, all contributions from the other two projects will be visible.

Hope this helps,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

bruno.bobichon · Answer

Arff, it's little bit ennoying .

1/ seems to have too many source of error

2/ I don't understand really, any tuto? We want to know what were tickets included into V1.2, v1.3 software version even if tickets comes from other projects,

3/ Not possible, ie projects are linked to specific customer, but corrected issues impact or std software (contained into another project itself)

do not know if i'm enought clear ;)

Ravi Sagar _Sparxsys_ · Answer

Hi @bruno_bobichon

Versions are project specific.

There are few options though.

1. You can create the version with same name in all the projects but those versions are still different and project specific. There are apps or automation you can use to sync the versions.

2. If your deliverables are in different projects then may be create a project to store your Epics. Have versions on the Epics, create a common board with various projects. This will only ensure versions on the Epics not to issues under it.

3. Just use one project, which may not be ideal for different teams and managers.

If you don't want to restructure then create a version with the same name in all your projects might be the best options.

4. You can also use a custom field in those projects.

Ravi