Jim M _Cahaba Forge_ Atlassian Partner

This isn't really the same thing as a native automation with JQL. A single rule that fires once after 7 days has the same problem. Miss that one reminder and you're back to needing someone to notice in a status meeting, the exact failure mode the article opens with. Cadence is also where native automation runs out of road:…

@Bartosz Stankiewicz - Jira Standard, but I don't see anything in Atlassian's docs that ties this to a specific plan, so I can't confirm tier-gating one way or the other. My guess is this is a staged rollout rather than a plan restriction. I have the approval required check box when creating a release, but do not see the…

Jira now has a native approval gate on releases. It's a "Require approvals before moving to Released" checkbox in the Create Release modal (new enough it still carries a "New" tag in the permission scheme), paired with an Approvers section on the release record. It has to be turned on at creation time. I couldn't find any…

@Robert Nadon , @Elena Lurye - What a brilliant idea! Really clever way to turn onboarding into something people actually want to do!

@Rune Rasmussen - Turning the requester into a second nudge path costs nothing, and it surfaces the absence problem earlier than any reminder schedule would. That's the one point here I have a partial answer for. The app ships a "My Approval Requests" dashboard gadget: a requester sees their open issues that have approvers…

@Natasja Eloff - thank you so much for breaking down how you handle JSM approvals! That gives me a much clearer picture of how admins navigate this in real environments. That automation workaround for timestamps makes total sense given the filtering limitations in JSM. Same with copying details into the description to get…

@Rune Rasmussen - this is a fantastic breakdown, thank you for taking the time to detail these! You've highlighted some really deep operational challenges that native workflows struggle with. A couple of quick thoughts on what you mentioned: * Reminders: You hit the nail on the head here. The "single email that gets…

Got it, that distinction makes total sense! That helps a lot as I look at how panel apps interact with portal-only permissions versus internal licenses. Thanks again for taking the time to break down your setup!!

Thanks for breaking down how you handle JSM approvals. That gives me a much clearer picture of how admins navigate it in the real world. That automation workaround for timestamps makes total sense given the filtering limitations in JSM. Same with copying details to the description to get around those fixed notification…

Hi @Nicoleta Mircea, I'd build on @Melika-Everview's answer, because she named the thing that actually gets an evidence pack accepted (the bundle you hand an auditor to prove a control worked): auditors care less about the volume of history and more about sequencing and integrity. Did the approval happen before…