Support

Email support@tiraisoft.com. What to put in that message is below — most of it is one row you can copy out of the app.

What to send

When something has gone wrong with a schedule, open the rule's History first. Every run is recorded there with the issue it created, or with the reason it did not — a skipped run, a day moved off a weekend or holiday, a subtask Jira refused. A weekend or holiday the rule is set to skip creates nothing and leaves no row in the history.

Quoting that row and the rule's name is usually enough for us to answer without needing access to your site. If the row shows a failure code, include it; what each one means is on the troubleshooting page, and several are things you can fix in a minute without waiting for us.

Worth checking first

Feature requests and bug reports

Both are welcome at the same address. For a bug, the History row and the rule's name are the two things that make it reproducible; for a request, what you are trying to schedule is more useful than a proposed setting.

The privacy policy covers what the app stores and where — the short version is that nothing reaches us at all. End user terms are Atlassian's standard set.