Small apps for Jira and Confluence

There are 4 apps here. Each one was built to fix a single thing the existing apps miss.

Exporter for Confluence

"Export a page and its child pages to HTML / Markdown with images embedded and tables intact. Print to PDF from your browser."

Recover for Jira

Records deleted issues and brings them back. Search who deleted what and when, and restore into any project.

Approve for Confluence

Ties an approval to a specific version of a page, not to the page itself. If the page is edited after approval, the badge takes back "approved" on its own.

Jira Export

Exports issues in a format you can print straight to PDF. No templates to write. The issue limit is stated, not hidden.

What all of them have in common

Failures are not hidden. When nothing can be shown, the screen tells you how many items matched and why they could not be displayed. You are never left staring at a blank screen.
What the app cannot do is said up front. Anything that cannot be restored, images that could not be embedded, counts that were cut off — all of it is stated explicitly.
There are limits on the count and on the time. The number of items loaded is capped so that the app does not freeze up on a large project. A count alone is not enough — Atlassian cuts an app's processing off at 25 seconds, so there is a time budget as well. When a limit is reached, the app shows what it did retrieve and puts on screen what is missing. That is always better than a screen that returns nothing.
Show the change before writing it, and let it be undone afterwards. The apps that change dates put the old value next to the new one for you to confirm before they write, and anything written can be undone in one click. You can also set them to read-only.
If you cannot see it, the app does not see it either. Both the lists and the exports are limited to the projects and pages you have permission to view, and the number of items excluded is shown on screen.
Settings can only be changed by the people who can administer them. Settings that affect what other people see — read-only mode, or which projects get recorded — can only be changed by someone who can administer that project. The export apps store their settings per person, so they never affect anyone else in the first place. The approval app is the one exception, because it has no way to make that check: instead it records who changed a setting and when, and shows that in the settings section of the approval ledger.
They work without a mouse. Dates can be moved by keyboard as well as by dragging (Tab to select, then ← →). The confirmation and the undo are exactly the same as when you drag.
No data goes anywhere else. All six talk to nothing other than Atlassian. Both the app source and the build output that actually gets uploaded are scanned mechanically every time to confirm it.