Looking for some guidance to help solve a grouping use case.
We are looking to solve a Release Management scenario that involves using both component and fixVersion.
Component are going to act like package versions ( PRODUCT v9.3.1, PRODUCT v9.3.2…) each story that is planned for a release will have the component/package assigned to the story that the code was delivered in, but not a fixVersion.
Key-component/version
• Story #1-PRODUCT v9.3.1
• Story #2-PRODUCT v9.3.1
• Story #3-PRODUCT v9.3.2
We want to cut a release using fixVersion that includes stories from both component versions, eg. Release 25.2.20… which contains component/version PRODUCT v9.3.1 and PRODUCT v9.3.2
Data for this structure looks like this:
Project in (APPLICATION) and ((fixVersion in unreleasedVersions() and fixVersion is not EMPTY) OR component is not EMPTY)
Was thinking to crosslink component/version to release fixversion via a ReleaseManagement issue type. That will have both fixVersion=”Release 25.2.20”and components (“PRODUCT v9.3.1”,”PRODUCT v9.3.2”)
Looking for a formula that finds the fixversion of the Release Mangement that shares the component version of the issue that I am on. This way I can group based on this formula version.
Kind of like this:
Release 25.2.20
• Release Story #1-“PRODUCT v 9.3.1”,”PRODUCT v 9.3.2”, Release 25.2.20
• Story #1-PRODUCT v 9.3.1, formula ->Release 25.2.20
• Story #2-PRODUCT v 9.3.1,formula ->Release 25.2.20
• Story #3-PRODUCT v 9.3.2,formula ->Release 25.2.20
Any suggestions would be helpful.
