Agile Hive Migration Scope

Agile Hive Migration Scope



Overview

This page outlines the scope and rules for migrating various fields and hierarchies from the source system to the target system. It covers the migration of Issue Hierarchy, Custom Field Values, WSJF Fields, Objective Fields, and Risk Fields, along with how the data is processed during migration.

Migration Scope

1. Issue Hierarchy

  • The migration includes both valid and invalid hierarchies, regardless of the project hierarchy in the source system.

  • The hierarchy structure from the source will be preserved in the target system, regardless of the project's configuration.

2. Custom Field Values

  • All custom field values are migrated regardless of the screen configuration. This means no custom field values are omitted during the migration process based on whether the field is visible or not on specific screens.

3. WSJF Fields

  • The following values are migrated for input fields in the WSJF calculation:

    • 1, 2, 3, 5, 8, 13, 20, 40

  • Value of 0 is converted and migrated as 1.

  • The migration includes the following specific fields involved in the WSJF calculation:

    • Job-Size

    • User Business Value

    • RROE

    • Time Criticality

  • The WSJF Value is calculated based on these fields.

4. Objective Fields

Plan Business Value

  • Only values 1-10 are migrated.

Actual Business Value

  • Only values 1-10 are migrated.

Uncommitted Objective

  • Only the values "Yes" and "No" are migrated.

5. Risk Fields

(Residual) Impact

  • Only the following values are migrated:

    • Unspecified

    • Catastrophic

    • Major

    • Moderate

    • Minor

    • Insignificant

(Residual) Probability

  • Only the following values are migrated:

    • Unspecified

    • Almost certain

    • Very likely

    • Likely

    • Unlikely

    • Very unlikely

(Residual) Exposure

  • This value is calculated in Agile Hive for Jira Cloud based on the Impact and Probability fields after the migration process.

6. Teams and PI Involvement

  • Both Teams involved and PI Involvement are calculated fields in Agile Hive for Jira Cloud.

  • The migration preserves the calculated values as per the defined logic in the source system.

Conclusion

This document summarizes the migration scope, detailing how various fields and values are handled during the migration process. For further questions or clarifications, please contact the support team at https://agilehive.atlassian.net/servicedesk/customer/portal/1/group/1/create/12.

 


 

Related content