Issue Summary

When restoring a production database to prepare a Stage Test environment with Production data, following the instructions for Creating a test environment for Jira, it is missing detailed steps to remove OAuth and Jira ID from the MS Teams integration.

The documentation should include the steps from the KB [Microsoft Teams for Jira has the same OAuth key and ID after migration to avoid Production impact when another environment is created using the same keys.

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Configure Jira environment using Atlassian's plugin Jira integration for Microsoft Teams
2. Follow the documentation to configure MS Teams integration
3. Observe the Jira ID generated in this environment - This Jira ID will be requested from Microsoft Teams users during authentication.
4. After testing, use the instructions from https://confluence.atlassian.com/adminjiraserver/creating-a-test-environment-for-jira-966063324.html to prepare a staging environment;
5. Configure MS Teams to reach the stage environment
6. It will ask to Configure the connection and authorize access to Staging Jira, confirming the Jira ID.
7. Observe that the JIRA id used is the same that was used on the Production
8. Now, disconnect from staging and try to connect with production again

Expected Results

Previous connection to production would be available

Actual Results

The authentication process goes to the staging environment instead.
Uninstalling the plugin does not fix the problem, the same Jira ID remains

Workaround

We need to manually remove data from the database following the steps from the KB Microsoft Teams for Jira has the same OAuth key and ID after migration