Attachment Policy Guard for Jira: 75-second demo script

Script and shot list only. No demo video recording is included. Capture only on the development Jira site with synthetic test attachments and a test issue; never use a customer site or real customer files.

Use a 1920 × 1080 browser capture, English on-screen captions and no Atlassian logo or product mark as a video title card. Show the current Jira interface in the app itself. Do not imply the app blocks an upload before Jira accepts it.

1. 00–07 sec — Set the context. Show Jira settings → Apps → Attachment Policy Guard. Caption: “Set file-type rules for new Jira attachments.”
2. 07–17 sec — Show the policy. Show a site rule and a project override with report mode selected. Caption: “Start in report mode. A match is recorded; nothing is deleted.”
3. 17–28 sec — Demonstrate signature checking. On the dev site, use a harmless synthetic test file whose filename extension differs from its test signature, then show the policy result. Caption: “The app checks available file bytes as well as the name.”
4. 28–39 sec — Review the audit entry. Show the match, detected type and report-mode result. Caption: “Review matches before turning on enforcement.”
5. 39–51 sec — Confirm enforcement. Show the enforce-mode confirmation and its recent-match count. Caption: “An administrator must confirm enforce mode. Deletion requires an active Marketplace licence.”
6. 51–65 sec — Show a test event. Add the synthetic file to a disposable test issue; show it being removed after Jira accepts the upload and the optional note, if that setting is enabled. Caption: “A matching attachment is removed after its event is processed.”
7. 65–75 sec — Close on the audit. Show the resulting audit row and CSV export control. Caption: “Audit entries use a 90-day storage TTL. File contents are not stored.”

Recording gate: A person must record and review the real app flow before this script can be described as a demo video. Restore report mode on the test site after capture.