Shreyas@Quietmill Atlassian Partner

Approvals are one of the most-asked-about features in Jira Service Management — and one of the least documented end to end. This guide covers the whole lifecycle: how approval steps actually work, who can approve, what approvers experience, how to track pending approvals, why approvals stall, and every real option for…

Your service desk sends a customer an update. A few moments later, a new request appears in the queue: Automatic reply: I am away until Monday. The reply is not asking for help. An agent still has to open the ticket, read it, make sure nothing important is buried inside, and close it. One ticket is a small interruption. A…

Disclosure: I build Approval Nudge at Quietmill. You can open the request in Jira. Its approval still says pending. But Approval Nudge cannot read the approval details, so nobody gets a reminder. On some migrated or integration-created requests, the missing piece is the request type. The work item exists, but the JSM field…

Disclosure: I build AutoReply Guard at Quietmill. AutoReply Guard is now available on the Atlassian Marketplace. We built it for Jira Service Management teams that regularly close requests caused by automatic emails. An out-of-office reply arrives as a new request in Jira Service Management. An agent opens it, reads it and…

Disclosure: I build Approval Nudge at Quietmill. Deactivating the account does not remove the person from an approval already waiting for them. An approver leaves the company on Friday. Their Atlassian account is deactivated. On Monday, Jira still shows their name on a request waiting for their decision. Nothing has gone…

Disclosure: I build Approval Nudge at Quietmill, the app discussed in the second half of this article. A JSM request says Waiting for 2 approvals. The approver source is a group. That sounds clear until the request stalls and an admin asks the question that matters: which two people are still expected to answer? The group…

Disclosure: I build Approval Nudge at Quietmill, the app discussed below. Someone books two weeks off. Their out-of-office turns on. Jira keeps waiting for that same person to approve a laptop, an access request or a change. Nothing is technically broken. Nothing moves either. The requester waits, the service desk chases,…

If you automate reminders, escalations or reports around JSM approvals, you probably start with approvals = pending(). It sounds definitive: Jira says an approval is pending, so someone must be waiting to answer. On a mature site, that is not always true. The query can find work nobody should chase, while other requests…

Disclosure: I build an approvals app for JSM. Nothing in this guide needs it — everything below is native configuration. The complete guide gives the short version of this topic: don't let requesters populate the Approvers field directly. This is the long version — what Jira actually lets you lock down, where the walls…

Disclosure: I build an approvals app for JSM. Nothing in this guide needs it — everything below is native behaviour. The complete guide gives group approvals a short section: set a group as the approver source and two behaviours surprise admins — members are notified individually, and the view of who has already approved…

Disclosure up front: I build one of the options below. It's the last one, and it's flagged where it comes up. The other three work without it. Jira Service Management emails each approver once. That's it — one email, sent when the request lands in the approval status. No reminder the next day, no weekly digest, nothing…

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. -…