Support

Contact: info@flowsmiths.app Hours: Monday to Friday, 9:00–17:00 Central European Time Response time: within 2 business days; we answer in English or Czech Security reports: security@flowsmiths.app (see Security)

When you write, it helps to include:

• your Jira site address and the app version (Jira settings → Apps → Manage apps → Expiry Tracker);
• what you expected and what happened;
• for missing issues: the "Last run" lines from the Expiry Tracker settings page;
• for the SSL agent: the output of ./expiry-agent.sh expiry-agent.env.

Please do not send agent tokens or passwords. We never ask for them.

Frequently asked questions

No issues are created. A Jira administrator must choose a project and an issue type in the app settings. Use "Send test issue" there to check it, and "Run check now" to see the result immediately.

The domain date says "unknown". Some registries (for example .de, .io, .eu) do not publish expiry dates in a machine-readable way. Enter the date manually; the item shows a note explaining this.

SSL dates are not updated. SSL certificates are checked by the agent script on your network. The settings page shows when it last reported. If it has not reported for 48 hours you also get a Jira issue.

Can I change when issues are created? Yes, in the settings: up to five thresholds between 1 and 365 days.

Does it work on Jira Standard / without Assets? Yes.

Where is my data? In Atlassian's Forge storage for your site. See the privacy policy.

How do I get my data out? "Export CSV" on the app page.