Requirement Drift Guard — Field Change Tracking for Jira

Built for teams where requirements keep moving after development starts. The baseline is captured automatically on the first transition to In Progress - no manual snapshots. Works with custom workflows (status categories, not status names), on Scrum and Kanban boards alike. A-to-B-to-A edits collapse to no net change while the full history stays visible. Currently watched fields: Summary, Description, Priority - per-project field configuration is on the roadmap. Built on Atlassian Forge: no external servers, no data egress, no AI, no tracking. Support: https://dangelstudio.de Why teams use it: developers stop building against stale requirements, product owners see which changes still need a decision, and scope creep becomes visible the moment it happens - not at sprint review.