Feature dependencies based on Requirement dependencies

Our engineers have a good view into Jira issue dependencies. Our business process enforces that all Jira issues will belong to a Jira Epic. We then map those Jira Epics into Aha Features. We would like the Jira Story/Task/Bug dependencies to be rolled up into Aha Feature dependencides.

• Our engineers use Jira to track their work. The create issue links between non-Epic issue types (e.g., Story, Task, Bug) to indicate dependencies. They do not create issue links between Epic records.

• Our product managers use Aha! to track Features integrated with Jira Epics.

• If an engineer creates a Jira dependency between two Jira issues that are part of different Epics, I would like to see the corresponding Epics' Aha! Features linked with a relevant record link.