- About TestFLO
- Overview
- For whom
- Key benefits
- Roadmap
- Onboarding
- Basic concepts
- Glossary
- Quick guide for Jira Administrator
- Quick guide for QA manager
- Quick guide for testers
- Demo environment
- Requirements
- Requirements
- Requirement operations
- Designing tests
- Test Case Template
- Organizing tests
- Reporting & tracking
- Reporting and tracking overview
- Requirement Test Coverage Report
- Requirement Traceability Report
- Requirement Test Execution Report
- Test Plan Execution Report
- Test Plan Iterations Report
- Test Execution Report
- Test information panel
- Issue panels
- Export test issues
- Dashboard Gadgets
- Miscellaneous
- TestFLO menu
- Issue Search Dialog
- JQL functions
- Administration & Configuration
- Projects' organization
- Create project
- Project configuration
- TestFLO settings
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Import/Export TCT
- Test Automation configuration
- Upgrade reports
- Upgrade guide
- Integrations
- Confluence
- REST API
- Configuration Manager for Jira
- Xporter
Last updated Jul 12, 2022
How does Configuration Manager work with TestFLO
Configuration Manager facilitates the migration of Jira and TestFLO configuration and issue data on the same or to a different Jira instance. For this, it uses special snapshots in three categories:
- System Configuration snapshot
- Project Configuration snapshot
- Project with Issues snapshot
After generating the appropriate snapshot, you can recreate the configuration from the source on the target Jira instance. Below are listed the existing rules for TestFLO objects broken down for each type of snapshot.
System Configuration snapshot
TestFLO object | Deployment Modes | |
---|---|---|
Merge Configuration | Restore Configuration | |
TestFLO Global Settings | Configuration is overwritten from the snapshot. | |
TestFLO Global Permissions | Configuration is overwritten from the snapshot. | |
TestFLO Project Configuration |
Configuration is overwritten from the snapshot.
The following rules apply to the Steps statuses:
|
Configuration is overwritten from the snapshot.
The following rules apply to the Steps statuses:
|
Preconditions repository |
The following rules apply:
|
The following rules apply:
|
Test Repository tree |
The following rules apply:
|
The following rules apply:
|
Custom fields context |
Configuration is overwritten from the snapshot.
Not supported:
|
|
Workflow advanced configuration | Configuration is overwritten from the snapshot. | |
Panel Filter Result configuration |
The following rules apply:
|
Configuration is overwritten from the snapshot. |
Project Configuration snapshot
TestFLO object | Deployment Modes | |
---|---|---|
Merge Project | New Project | |
TestFLO Project Configuration |
Configuration is overwritten from the snapshot. The following rules apply to the Steps statuses:
|
Configuration is overwritten from the snapshot. |
Preconditions repository |
The following rules apply:
|
Configuration is overwritten from the snapshot. |
Test Repository tree |
The following rules apply:
|
Configuration is overwritten from the snapshot. |
Custom fields context |
Configuration is overwritten from the snapshot.
Not supported:
|
|
Workflow advanced configuration | Configuration is overwritten from the snapshot. | |
Panel Filter Result configuration |
The following rules apply:
|
Configuration is overwritten from the snapshot. |
Project with Issues snapshot
The same rules apply for the Project with Issues snapshot as for the Project Configuration snapshot. In addition, the following rule applies to the transferred data:
TestFLO object | Deployment Modes | |
---|---|---|
Merge Project | New Project | |
Issues and custom field data |
TestFLO issue data is imported from the snapshot.
The following rules apply:
|
Configuration is overwritten from the snapshot. |