Create Aha! record links and dependencies

Regardless of the size of your team or the complexity of your roadmap, you will come across portions of work that relate to or depend on each other. It can be incredibly useful to create links between Aha! records that allow your teammates to dig in for further context, and to visualize these links in reports and roadmaps.

In Aha! the following record types can be linked to each other:

  • Goals
  • Initiatives
  • Releases
  • Release phases
  • Release milestones
  • Master features
  • Features
  • Ideas
  • Notes

Create record links

  1. To create a record link, open the detail view for a record and click the More options button in the upper right hand corner.
  2. Then, click Link to another record to open the Record link modal. aha-strategy-link-records-modal.png
  3. The Relates to dropdown gives you options for the type of record link you want to establish and the These <records> dropdown allows you to select the record type to search for in the Choose field.
  4. Begin typing a record's reference number or title, then select the record(s) from the search suggestions that you'd like to link. Click Create link to create the link. 

Select a record link type

Your record link can be any one of six types. 

  1. Relates to
    This is the most generic relationship. When a record is related to another record in some way that's not easily defined by the other categories, but you want to show that relationship, you can use Relates to.
  2. Depends on / is a dependency of
    This is the most commonly used relationship and it's the only link you can create on the Release > Gantt view by dragging and dropping between two records (features, release phases, or release milestones). This is stating that one record must be completed before another one is started. If the due date of record A gets pushed out, it will automatically move out the start and due date for record B to accommodate the new schedule.
  3. Duplicates / is Duplicated by
    Occasionally, you may want to track duplicate work. For example, if you have two products and both will use the same feature, you may still need to track the feature in both product roadmaps. The work only happens once so you should create a primary feature where the work will be done, and then create a second feature and link it to the primary. This helps you report on but also keep track of the work.
  4. Contains / is contained by
    If you are working on a record that will be part of another record, use this link to show the relationship. For example, you might be creating an alerting capability that's triggered by a report. You create the reporting capability in one feature but link it to the other feature for alerting capabilities.
  5. Impacts / is impacted by
    This could represent a record whose work will ultimately impact the design of another record (but does not create a dependency). In this example, you may wish to hold off on your design until the first record's design is completed. 
  6. Blocks / is blocked by
    This could represent a record that completely blocks another record, because until you complete the first, absolutely no work can take place on the second record. Another example is that this record uses a resource that you need — the development team's time, for example — and until it's completed, you are blocked. This relationship could be helpful in reporting tradeoffs you've made during the roadmapping process. 

Once you have created a record link, you can see it on each record's Record links section. Click one of the hyperlinks to see the detail drawer for the linked record. 


Visualize record links

Now that you have linked one or more records together, it is time to visualize them. 

Click the Visualize button next to the Record links section of one of your records. You will see an interactive dependency map that allows you to click into any of the linked records, and expand or collapse the dependencies of records linked to yours. 


Report on record links

The following options are available for reporting on record relationships:

  • View dependencies for multiple objects at once using the dependency report.
  • Dependency relationships between initiatives can be visualized on the strategy roadmap.
  • Dependency relationships between features, phases, and milestones can be visualized on the Releases > Gantt view or on Roadmaps > Dependency.
  • Initiative, release, release phase, feature, and idea reporting tables include columns for Record links, which can then be included in the list, pivot, chart, and custom roadmap reports.


With any of these visualizations, use the More options button to share the information with your team as an image, PDF, or Aha! presentation.

Was this article helpful?
0 out of 0 found this helpful