Support

Email support@tiraisoft.com. We answer within one business day, Monday to Friday.

What to send

When something has gone wrong with a schedule, open the rule's History first. Every occurrence 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.

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

• A rule did not create an issue — the ordered list of causes, most of which the History answers outright.
• Setup — if the app tab is missing from a project, or the controls are not editable, that page explains both.
• Writing and running rules — every field in the editor.

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.

Terms and privacy

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.