NF / Atlassian
Config Watch
Track relevant Jira configuration changes.
Config Watch records who changed what in Jira configuration — workflows, schemes, fields, permissions — and surfaces the changes that actually matter.
This product is planned. Scope below describes intent; details, pricing and dates are published via changelog when a build ships.
Config Watch — product interface
NF / Problem
What problem does this solve?
Nobody knows who changed that workflow last Tuesday.
Jira configuration drifts: quick fixes, overlapping admins, undocumented tweaks. When something breaks, forensics are painful. Config Watch keeps a calm, filterable record.
NF / How it works
3 steps, no platform.
- 01ObserveSnapshot relevant configuration areas.
- 02DiffCompare snapshots and highlight meaningful changes.
- 03NotifyAlert the right people about risky edits.
NF / Features
What it does.
Only shipped behaviour is marked active. Beta and planned items are labelled honestly.
- planned
Change timeline
Chronological, filterable config history.
- planned
Risk flags
Highlight permission and workflow edits.
Built for
- Jira admins
- Platform teams
NF / FAQ
Questions, answered plainly.
What does it monitor?
Core configuration surfaces relevant to stability. The exact scope is documented per release.
Config WatchNF / Support
Need help with Config Watch?
Docs, troubleshooting and a direct line to the people who build it.