Support – Migration Doctor for Jira Cloud
- E-mail: support@687.monster
- Hours: Monday to Friday, 9:00–17:00 CET/CEST, excluding Polish public holidays.
- Response time: first answer within 2 business days; security reports within 2 business days with priority handling.
- Languages: English and Polish.
Before you write
Please include:
- Your Jira Cloud site URL and your Jira Data Center version.
- The snapshot script version and the command you ran (without tokens).
- The check ID and the object name of the finding you ask about.
- The message shown in the app, if any.
Never send snapshots, tokens or passwords by e-mail. If we need to look at a problem in a snapshot, we will ask for a minimal, anonymised example.
Common answers
- The file is rejected. The app lists each problem with its place in
the file (for example
filters[12].jql is required.). Re-run the latest snapshot script. - Many filters are reported as missing. Check the snapshot's coverage: without the SQL export the script cannot list other users' filters, and without the Cloud admin override private Cloud filters are invisible. Findings with low confidence say so.
- A user is not matched. Matching uses e-mail only. Set the right Cloud account under Users, or mark "no Cloud account", and run the checks again.
- A repair is blocked. The preview lists the reason: a user without a Cloud account in the JQL, a project or status missing in Cloud, or JQL that Jira rejects.