With some configuration, all of the above has occurred successfully so far.
Now, as we endeavor to deliver incremental value, we have identified milestone slices that we want to work collaboratively together to rollout our product often. This seems like a perfect use for Cross-Project Releases (CPRs) but I'm experiencing some limitations that don't align with the documentation. I'm hoping this community can help me solve a way to organize tasks and stories across multiple Project into Release Versions, or CPRs, of delivery.
What is described at the bottom of this article is exactly what I want to do and would expect for this feature! Screenshot below for ease of reference:
However, we have the redesigned planning interface so the details in this article seem to be what I have to work with, instead. See screenshot #2 below:
The difference between these is not small! If I understand correctly:
Now I imagine we have identified four (4) milestone slices of delivery for our product and there are eight (8) Jira Projects collaborating, potentially more down the road. The manual intervention needed for this is just astounding!
Please tell me I've got it all wrong or there is a better idea out there! Thank you so much for your consideration.
Hello @yoni.degani ,
Thanks for reaching out. In the live plan view (old interface) the Cross project releases were created as an independent release in tandem with existing versions in the project so you would wind up with a project-specific version as well as a cross-project version specific to the plan only. The outcome was having duplicate effort by maintaining two overlapping versions, one for the project and one for the cross-project release.
However, in the new interface, the Cross project versions will take the existing project-specific versions and group them together with a tag to identify the cross project interaction of the previously independent versions as a single release item to avoid duplication of efforts.
Next for the naming convention question and drill-down and viewing of the releases I discussed this in the following thread but wanted to highlight one portion in particular noting that the cross-project releases can have different naming conventions per project but lump together for the Cross project flagged release:
For better drill-down and identification Cross project releases are tagged with a grey box next to the name to call them out as a cross-project release and make identification easier:
For the name portion this can be isolated for easier identification using the "View Settings" options and setting the "Group By" filter to "Release", under this view the issues are collected and nested under each release and again there is a Grey Box next to the release and they will then show the groupings and cross project releases like this:
Hope this info helps, and let me know if you have any additional questions.
For me what remains unresolved is how I can run queries on my cross project releases?
For example - release notes and or QA verification?
I'd like to use CPR's to group software suites, made of up individual software components with their own releases. it's these software suites that need to work together and thus are what QA need to verify against.
So how do I tell QA what tickets have been resolved in a suite of software using CPRs?
In the old mechanism, the one I tested with a while back it would have been quite easy to even create a board just for QA to progress verifications against a specific CPR, let alone any other queries.
Perhaps there is still a way to extract the CPR in a JQL query?
please let me know asap if there is
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events