Aldorock apps for Atlassian

Follow-ups for Jira

Remind yourself or a teammate about a work item on the day you choose, and nudge stale work on a schedule. Delivered as a comment that mentions the right people, so Jira notifies them the way it notifies any mention.

How delivery works, honestly

The app has no email server and no Slack connection, on purpose: it runs entirely on Atlassian's Forge platform with no outside services, which is what keeps your data inside Atlassian. When a follow-up is due, the app posts a comment on the work item that mentions the people you chose. Jira then sends them its normal mention notification, by email and in the Jira notification bell, according to each person's own notification settings. The comment is visible to everyone who can see the work item. Delivery happens on the hour: a follow-up due at 09:00 arrives between 09:00 and 10:00.

Follow-ups on a work item

  1. Open the work item, choose … → Remind me, or use the Follow-ups panel on the work item.
  2. Pick a date and time, in your Jira timezone. Presets: tomorrow 09:00, in three days, next Monday, in a week. A time already passed is delivered at the next hourly run.
  3. Choose who to mention: yourself, the assignee, the reporter, named people. If none of them resolves (for example an unassigned work item with "the assignee"), the comment mentions you.
  4. Write a note. It becomes the text of the comment.

Under Apps → Follow-ups you see every follow-up you set or are mentioned in, overdue first. Snooze moves the time; Done closes it without a comment; Delete removes it. A follow-up the app could not post (for example because the work item was deleted) shows as failed with the reason, and you can snooze it to retry.

Rules: scheduled nudges from a filter

A rule runs a JQL filter on a schedule and comments on each matching work item, mentioning its assignee, its reporter or a named person, with a message you write. Typical uses: "work items untouched for a week", "due date passed and not done", "waiting for customer for 3 days".

SettingMeaning
ProjectProject admins create rules for their own project; the JQL is automatically limited to it. Jira admins can create rules across all projects.
ScheduleEvery day or every week at a given hour in a given timezone. Runs happen on the hour.
MessagePlain text with variables: {{key}}, {{summary}}, {{assignee}}, {{reporter}}, {{status}}, {{daysInStatus}}, {{dueDate}}, {{priority}}. Blank line for a new paragraph; lines starting with "- " make a list.
Max comments per runA ceiling per run, 1 to 200, so a broad filter cannot flood a project. Default 50.
Quiet daysA work item is not commented on again by the same rule until this many days have passed. Default 7; 0 means every run.

Preview matches shows up to five current matches with the message rendered. Run now runs the rule immediately without changing its schedule.

Who can do what

ActionWho
Set a follow-upAnyone who can see the work item
Snooze, finish or delete a follow-upThe person who set it, the people mentioned in it, Jira admins
Rules for one projectProject admins of that project, Jira admins
Rules across all projects, run the scheduler by handJira admins

Limits

Where the data lives

Follow-ups and rules are stored in Forge storage in your Atlassian site's region. The app reads work items as you when you use it, and as itself when it posts due comments. See Privacy.

Changelog