RELATED IDEAS
Maintain integration links when Jira records move projects/boards AND sprints are mapped
What is the challenge? |
Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. This board will not necessarily remain the same when the record moves. |
What is the impact? |
When a record moves Jira projects, and thus boards, the integration link is not maintained because the board set in the template vs the child integration(s) no longer match |
Describe your idea |
Enable the integration links to be maintained, and sprints to be mapped, when records move to a different project/board. |
© 2025 Aha! Labs Inc.•All rights reserved
This feature is a no brainer for anyone managing multiple delivery teams in a scaled agile framework where multiple teams are executing against a common capability monitored under a single epic.
I'm honestly surprised this isn't native functionality already.
This is rather important to support any scaled implementation where teams work collectively to deliver solutions. Without this individuals will have to spend a lot of time manually linking records.