Support & documentation

Help with AB Apps

Setup guides and FAQs for both apps, plus a direct line to a real person. No ticket portal, no bots.

We aim to reply within two business days

Email us with your Atlassian site URL, the app name, and what you're seeing. We answer during EU business hours, typically much sooner than two days.

support@abapps.dev

Team Reminders for JiraSet a reminder on any issue — for you, the assignee, or specific teammates.

What it does

Team Reminders adds a Reminders panel to Jira issues so a follow-up actually happens. Unlike a personal reminder, you can remind the current assignee or specific teammates — not just yourself — and the reminder is delivered as an issue comment that @-mentions each recipient, so Jira sends its own notification.

Getting started

  1. Open any Jira issue. Find the Reminders panel on the issue (it is also available as a "Reminders" context glance).
  2. Choose who to remind: yourself, the current assignee, or specific people (pick one or many with the user picker).
  3. Pick a date and a 24-hour time (HH:MM). The time is interpreted in your own Jira timezone.
  4. Optionally add a short message for context (up to 500 characters).
  5. Save. When the reminder is due, the app posts an issue comment that @-mentions each recipient.

Tracking and managing reminders

  1. The on-issue list shows every reminder set on the current issue with a status lozenge — scheduled, sent, or error — plus the target and message. Delete any reminder in one click.
  2. On a reminder that has already fired, use +1 day to snooze it by a day rather than recreating it.
  3. Open My Reminders (a global page) to see everything you've created across all issues, split into Upcoming and Past.

Frequently asked questions

How precise is delivery?

A scheduled check runs once an hour, so a reminder is delivered during the hour you chose rather than to the exact minute. For chasing follow-ups, deadlines, and approvals this is by design — we'd rather be upfront than over-promise minute-level precision.

Who is "the current assignee"?

It is resolved at the moment the reminder fires, so if the issue changes hands before then, the person assigned at that time is reminded. If the issue is unassigned when the reminder fires, it falls back to the reminder's creator.

Do the people I remind need to install anything?

No. Delivery is a normal Jira issue comment with an @-mention, so Jira handles the notification and email. Only the person creating reminders needs the app open.

Why 24-hour time?

To remove AM/PM ambiguity. Enter the time as HH:MM. Reminders set to a time in the past, or with an invalid date/time, are rejected.

Does it support recurring reminders?

Not currently — each reminder is one-time. You can snooze a fired reminder by +1 day. Recurring reminders may come in a future version.

Where is my data stored?

Only in Atlassian-hosted Forge storage inside your own Jira instance. The app makes no external network calls and sends nothing to us or any third party. See the Privacy Policy.

Permissions requested: read:jira-work, write:jira-work, read:jira-user, storage:app — the minimum needed to read the issue, post the reminder comment, resolve recipients, and remember your reminders.

Approval Nudge for JSMKeep pending Jira Service Management approvals moving — automatically.

What it does

Approval Nudge watches pending approvals in the Jira Service Management service projects you choose and posts a reminder comment that @-mentions the approvers who still need to act. If an approval keeps waiting, it can escalate to a named contact — with no automation rule for you to build or maintain.

Getting started

  1. Open the Approval Nudge configuration (a global page) and select the JSM service projects to watch.
  2. Set the nudge cadence in hours (default 24; minimum 1) — how long the app waits between nudges on the same approval.
  3. Optionally set Escalate after a number of days (default 3; set to 0 to never escalate) and choose an escalation contact.
  4. Optionally enable "Also post a customer-visible portal comment" to reach portal-only approvers by email (off by default).
  5. Save. An hourly scan then finds open requests with pending approvals and nudges the approvers.

The per-request glance

  1. Open any request. The Approval Nudge glance shows each pending approval with days waiting, the nudge count, and the last-nudge time (shown in UTC).
  2. Use Nudge now to send a reminder immediately, outside the normal cadence.
  3. If the request isn't a JSM request or has no pending approvals, the glance shows "No pending approvals on this request."

Frequently asked questions

How often will it nudge?

At most once per approval per cadence window. A newly created approval waits one full cadence window before its first nudge, so people aren't nudged the instant an approval appears. The scan is idempotent and catch-up-safe.

How does escalation work?

If Escalate after is greater than zero and an approval has been waiting at least that many days, the escalation contact is added to the mention (once) so the right person is looped in. Set it to 0 to disable escalation.

What is the customer-visible portal comment?

Optional and off by default. When enabled, in addition to the internal @-mention comment, a public portal comment is posted so portal-only approvers (who may not see internal comments) are reached by email.

Does it email approvers directly?

No. It posts comments; Atlassian / Jira Service Management generates the notifications. Licensed approvers get native notifications from the internal @-mention; portal-only approvers are reached via the optional public portal comment.

Is there a stability caveat I should know about?

Yes, in the interest of honesty: pending-approval data is read via Atlassian's JSM approvals API, which Atlassian currently designates as experimental and may change. We track Atlassian's changes and update the app, but this is worth knowing for a business-critical workflow.

Where is my data stored?

Only in Atlassian-hosted Forge storage inside your own instance — your project selection, cadence and escalation settings, and per-approval nudge timestamps. No external egress. See the Privacy Policy.

Permissions requested: storage:app, read:jira-work, write:jira-work, read:jira-user, read:servicedesk-request, write:servicedesk-request — to find open requests, read pending approvals and approvers, post nudge/escalation comments (and the optional portal comment), and remember your configuration and nudge history.

Still stuck?

Email support@abapps.dev with your Atlassian site URL, the app name, and a short description (a screenshot helps). We aim to reply within two business days, EU hours.