Moving records with Jira or Rally

The two-way integration between Aha! and your development system keeps product management and engineering teams aligned as progress is made on your product. When you send a record from Aha! to your development system, updates begin to flow back and forth as your latest improvement passes through each stage of development.

As your product evolves, records will occasionally need to be moved:

  • A user story may need to move from one development project to another
  • A master feature, feature, or requirement may need to move from one product to another
  • Parent and child records may be sent to the development system before or after one another, then moved to a new project

To ensure that your records are always up to date, we support the most common use cases for moving records with Aha! and your development system.

Note: The following scenarios apply to master features, features, and requirements that are linked with Jira or Rally. For the purpose of this document, these two systems will be referred to as the “development system.” 

Aha-moved-linked-records.png

Prerequisites

All of the following prerequisites must be met to move master features, features, and requirements between products in Aha! or projects in your development system:

  • You must be using the same development system server for all projects.
  • You must have an integration set up on each product in Aha! for every project in your development system that may contain records which are linked.
  • You must be using the same integration template for each integration that you set up.
  • For Jira integrations, you must be using the same webhook for each integration.
  • You must be using Aha! integrations 2.0 with Jira or Rally.

Scenario 1: A user moves a record in the development system which is linked to an Aha! record from one project to another.

Example: You have a product in Aha! called Product A. This product is integrated with Project 1 and Project 2 in your development system. Your team creates a feature in Aha! and sends the feature to Project 1. Your team starts grooming the feature. During the grooming, it is determined which team will work on the feature. The record is moved to Project 2 in the development system. The link between Aha! and the development system remains intact for this record and the mapping will adjust using the integrations that are set up for Product A.

Scenario 2: A user sends a parent record with child records from Aha! to the development system, then moves the child records to other projects.

Example: You have a product in Aha! called Product A. This product is integrated with Project 1 and Project 2 in your development system. Your team creates a master feature with a handful of child features in Aha! and sends it to Project 1 to be groomed and assigned to a development team. The features are moved to Project 2 in the development system. The link between Aha! and the development system remains intact for these records and the mapping will adjust using the integrations that are set up for Product A.

Scenario 3: A user sends a record to the development system and creates or moves child records to a different project

Example: You have a product in Aha! called Product A. This product is integrated with Project 1 and Project 2 in your development system. Your team creates a feature in Aha! and sends it to your development system. Your team then breaks out the work by adding or moving requirements to Project 2. These child records can be imported into Aha!, their links will stay intact, and the mappings will adjust to use the integrations that are set up for Product A.

Note: Aha! will automatically import child records if the Automatically import new records option is selected on the Settings > Product > Integrations > (Select an integration) > Enable step.

Scenario 4: A user moves an Aha! record which is integrated with your development system from one Aha! product to another.

Example: You have a product in Aha! called Product A. This product is integrated with Project 1 in your development system. Your team creates a feature in Aha! and sends it to your development system for grooming. During the grooming, it is determined that the feature needs to be moved to Product B. You move the record to Product B. The link between Aha! and the development system remains intact for this record and the mapping will adjust to use the integration that is set up for Product B.

Scenario 5: A user sends child records to the development system, then at a later time, sends a parent record that is linked to the child records.

Example: You have a product in Aha! called Product A. This product is integrated with Project 1 in your development system. The team creates features in Aha! and sends them to the development system. After these features have been sent, you determine that the features actually align to an epic which has not yet been created. You create the master feature (epic) in Aha!, link it to the features in Aha!, and then send the master feature to the development system. The records in the development system will be updated to reflect the new parent record. If at any point the parent or child records are moved to a different project, the link between Aha! and the development system will remain intact and the mappings will adjust according to the integrations that are set up for Product A.

 


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