Recently, a customer requested guidance on how to sync a Jira Board with an unique Filter Query. The referenced filter query brought in multiple projects into a single team's scrum board and closely resembled this: project in (PA1, PA2, PA3, PA4) ORDER BY Rank ASC. This is how Jira Align can support this ask!
Begin with multiple Jira Projects with Team level scrum issues including the Story, Sub-Task, and Bug.
Pick a board from one of the 4 Projects and ensure the Filter Query is set as desired and the Filter Share is listed to the Project.
Questions on setting the filter share and why we set it can be found answered here:
Map all 4 Projects to Jira Align under Jira Align Admin > Jira Settings to the same Jira Align Program
Map only the Board where you set the Filter Share under Jira Align > Jira Management
Notes: Stories from all Projects on this board will map to the Jira Align team associated to the board (in this case PA4) 100% of time when assigned to an integrated sprint. Stories in the backlog will only map to the associated team when the issue originates from the Project set in the Filter Share (in this case PA4).
Please note you can only list one Project in the Filter Share in Jira or it will lead to a mapping error in Jira Align. To assign issues from the other Projects listed in the filter query to their appropriate team in Jira Align when they are located in the backlog you will need to setup custom team field mapping as referenced here:
I highly recommend using the single select list field type from Jira. You will need to setup the custom team field mapping for all Projects shared within the Filter Query.
This is what the custom team field should look like in Jira.
Your stories from the Jira Board will now sync to their associated Jira Align team regardless of their Project and Sprint assignment.
Note: I do not recommend this implementation due to its complexity and overall lack of guardrails for data integrity but it will work if users utilize the custom team field in Jira and do not integrate any additional boards from these Projects. If additional boards from these Projects are integrated the teams that work on those boards would also need to implement the custom field mapping for team.
Tim KeyesAtlassian Team
Lean Portfolio Management (LPM) is a relatively newer management methodology which draws from lean and systems thinking approaches to drive value-based outcomes, as opposed to more traditional techni...
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