I need to treat features from multiple Jira projects as part of a single release notion in Aha. The problem is that if I turn on two way release syncing when I mix items from multiple Jira projects the features/master features automatically get duplicated across all sync'd Jira integrations. This means I cannot effectively keep versions/releases in sync exclusively through Aha. My current work-around is to setup a one way sync from Jira and use a custom variable to denote an "intended" release which is synced. The problem with that is it becomes up to the Jira admins to make sure the items are tagged with the right release.
What I suggest is adding an option to prevent duplication of stories across jira integrations but still update the release field with the right release. As you see in the attached diagram I would like to drag stories from my parking lot releases (synced with the backlogs in JIRA) into my scheduled releases and have those features (stories) moved into the common release name in Jira without creating duplicates of the same story in all the other projects.
|Release time frame|
This is now possible when all integrations use the same integration template.
Check out this article to learn more.