Agile Board and Update Set Integration During Production → Development Environment Clone

[kuuum_aaaya]

Hello ServiceNow Community,

I'm seeking advice from anyone who has experience with maintaining the relationship between Agile Boards and Update Sets during production to development environment cloning.

Background:

Update Set related tables (sys_update_set, etc.) will be excluded during cloning

Development environment has custom integration between Agile Board stories and Update Sets via related lists

The clone process may break the relationship between stories and Update Sets

Production environment has Agile Board plugin installed but is not actively used

Potential Approaches:

Pre-export + Post-recovery (XML extraction → re-import after clone)

Re-establish relationships using production data

Discontinue the integration

Questions:

Which of the above approaches would be most effective?

If pursuing approach #1, what are the key considerations and potential pitfalls during recovery?

(Optional) Is it possible to exclude/preserve Agile-related tables during cloning even if they're not actively used in production? Target tables include: rm_story, rm_epic, rm_sprint, rm_release, rm_task, rm_scrum_task, sys_journal_field, backlog_definition

Any insights, experiences, or best practices would be greatly appreciated!

Thanks in advance for your help.