Form Drift Check
by ProfitSignal Labs

Form Drift Check — setup and review

Release in preparation. Installation from Marketplace is not yet available.

Start with a small scope

  1. Open Form Drift Check from Jira Apps. Use a Jira Service Management desk you can access.
  2. Enter the service desk ID and one or more issue keys, separated by commas or new lines. Start with one or two issues. Development tests must use fictitious data.
  3. Select Review linked fields. MATCH means supported values agree. EXPECTED_DIFFERENCE preserves a submitted snapshot; ACTION_REQUIRED follows the explicit matching policy. UNKNOWN and EXCLUDED are not successful comparisons.
  4. Open protected detail only when you need the compared values. Every action reads the source again. Results expire after one minute and do not update continuously.

Project policies

A project administrator can load rules, enter a linked Jira field ID and supported type, and save a policy. The first issue in the list validates that mapping. Rules apply across that project by field ID; per-template policies are not included. Each field has at most one rule, with at most 40 rules and 100 saved versions per project. Restore default policies adds a new empty version; it does not erase earlier versions.

Review and history

Record internal review offers an enumerated reason: snapshot confirmed, difference reviewed or follow-up required. It never changes Jira or resolves an issue. REVIEWED records that somebody reviewed the same source/rule fingerprint; it does not mean a follow-up is complete. Only the first history page contributes to this indicator, so older acknowledgements may not be reflected.

Save fresh snapshot metadata stores identifiers and classifications, not answers. Review history rereads source permissions. Missing or inaccessible form references are omitted. A project administrator can delete the displayed history page. Deletion removes whole stored records, so deleting one snapshot also removes its other observations. History has a 30-day logical lifetime; platform physical deletion can lag.

CSV and limits

Refresh access and prepare CSV runs new reads and shows copyable metadata, without source values. An export exceeding the budget fails without releasing a partial CSV. Files copied by users cannot be recalled. Reviews are non-atomic: permission or source changes after reading can only be detected on a later check.

Discovery lists at most 200 visible project issues. Reviews reserve a budget below 400 source requests and stop starting new work after 40 seconds; results expire after 60 seconds. A per-issue limit or access error releases no result for that operation. Narrow the list if it does not complete.

Unsupported fields and troubleshooting

Choices/multichoice, rich text, conditional visibility and external data connections are not evaluated. Missing data is not treated as a match. If access is denied, ask the Jira administrator to check the desk, issue, form and app-access permissions. For source changes, rerun the review. For a rule conflict, load the latest rules before saving again.

Support and erasure

Contact support@profitsignallabs.dev with the operation, approximate time and redacted error. Do not send tokens or Jira exports. Source records remain controlled by your Jira administrator. For stored configuration or inaccessible history that cannot be removed from the UI, request verified assistance through the support portal. No immediate deletion of platform backups is promised.