Features assuming the same release as its parent master feature when importing from Jira

Given that I have an epic in Jira, linked to a Master Feature in Aha

And the Master Feature is found in "Release X",

When I create a story beneath that epic in Jira,

Then the story should be imported as a child to the Master Feature, 

AND assume the same release as the Master Feature. 

 

Currently, depending on how an integration is set up, the feature is imported into the Parking Lot, or the first release (in chronological order), not the same release as the parent Master Feature.

 

This might make it a bit easier to find the newly created feature, as someone might not assume it would be found in the Parking Lot, or the earliest release. I would make the assumption it should sit in the same release as the master feature. 

  • Guest
  • Jan 6 2020
  • Future consideration
Release time frame
  • Attach files