Hi App Central — first post from Quietmill after joining the group this week.
We've just shipped Approval Nudge, and since this group appreciates architecture details, the trust bits first:
- 100% Atlassian Forge. No connect servers, no external infrastructure, zero egress — request data never leaves your Atlassian site.
- Minimal scopes, frozen by policy: storage, read/write work items, read users, read service desk requests. No admin scopes.
- It never makes approval decisions and never changes who your approvers are. Reminders, resends, escalation, reporting — nothing else.
What it does: JSM sends each approver exactly one email per approval — ever (the reminder request has been open on JSDCLOUD-8369 since 2018). Approval Nudge runs an hourly scan and closes that gap: reminders that target only approvers who haven't answered, re-delivery of the native approval email with its Approve/Decline buttons, escalation to a named contact when reminders cap out, and flagging of deactivated approvers so requests stop waiting on people who left.
Marketplace: https://marketplace.atlassian.com/apps/971596656/approval-nudge-reminders-escalation-for-jsm-approvals
We're a small UK studio (founder = 20+ years enterprise IT) doing the same play several vendors here have written about: pick one well-evidenced gap, build the smallest honest app that closes it, on Forge from day one. Feedback from admins running big approval volumes especially welcome — the roadmap is driven by evidenced pain, and this group is where the evidence lives.
