-
Suggestion
-
Resolution: Unresolved
-
None
-
232
-
Issue Summary
JCMA doesn't migrate 'Project automation rules' created using A4J while migrating Jira Software/JSM projects and only migrates the legacy automation rules included in JSM by default.
Steps to Reproduce
- Migrate JSW/JSM project with Project automation rules configured by A4J
- Project automation rules will not be migrated to the cloud
Expected Results
Project automation rules should be migrated to the cloud
Actual Results
Project automation rules fails to migrate to cloud
Workaround
Project automation can be manually migrated using import-and-export-jira-automation-rules
- is duplicated by
-
AUTO-325 Support the Migration of Automation Rules, e.g. to Cloud from Server/DC, when importing a JSON file exported from server - the import tool just spins but no error is shown on the UI, process rules and report on failures.
- Future Consideration
- relates to
-
CLOUD-11853 Support the migration of Automation for Jira rules with C2C Migration
- Gathering Interest
- causes
-
MOVE-106798 Loading...
-
MOVE-134925 Loading...
- is related to
-
MOVE-87754 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...