Support

Email support@clientportal-platform.com. We aim to reply within one business day.

Writing in about a problem? Please include your Jira site URL, the name of the rule, what you expected it to create, and what happened instead. The rule's History button shows the exact reason for every run, and pasting that into your email usually turns two days of back and forth into one reply.

Getting started

Install the app, then open Apps → Routine in Jira and press New rule. Pick a project, write the issue summary, choose a schedule in plain English, and save. There is no cron syntax to learn anywhere in the app.

Questions people ask first

When exactly does an issue get created?

On the day the schedule says, at or after the hour you chose, in the timezone you chose for that rule. We say "at or after" deliberately and it is worth understanding: Atlassian runs scheduled app code in batches rather than at an exact second, so the issue may appear a little after your chosen hour. It will never appear before it, and it will never be created twice for the same day.

What happens if Jira is briefly unavailable?

The rule tries again on the next hourly run of the same day, so a temporary problem fixes itself without anyone doing anything. The failure is recorded in the rule's History with the reason Jira gave.

Can I schedule "every two weeks" or "the first Tuesday of the month"?

Yes. Both, plus working days only, the last day of the month, and the last working day of the month. A monthly rule set for the 31st lands on the 30th in a 30 day month and on the 28th or 29th in February. It never rolls forward into the next month.

Can the summary include the date?

Yes. Put {{date}}, {{monthName}}, {{year}}, {{week}}, {{day}} or {{month}} anywhere in the summary or description, and they are filled in on the day the issue is created. So "Invoice run {{monthName}} {{year}}" becomes "Invoice run August 2026".

Who can create and see rules?

Jira administrators only. Rules describe work across every project on the site, so they are kept to administrators in the same way Jira keeps its own automation rules. Everyone else simply sees the issues appear as normal.

What if the person who created a rule leaves the company?

The rule carries on. Issues are created by the app itself, not by the person who set the rule up, so nothing breaks when someone changes teams or leaves.

Can I skip one occurrence without deleting the rule?

Yes. Press Skip next on the rule. It skips exactly one upcoming run and then carries on as normal. Press it again to skip the one after that too.

Does the app send email or use any outside service?

No. Routine makes no connections outside Atlassian at all. It declares no external permissions, which is why it carries the Runs on Atlassian badge on the Marketplace.

What happens when my subscription ends?

Rules stop creating issues, and the app says so plainly instead of failing silently. Nothing is deleted. If billing is restored, every rule comes back exactly as it was.

Reporting a security issue

Write to support@clientportal-platform.com with "security" in the subject and we will reply within one business day.