Recurring issues

Templates that create a new issue on their own every day, week or month.

Recurring issues that create themselves. A recurring issue creates the same task every day, week or month, in the project you choose and with its priority. You set it up once in Settings and the server does the rest. Watch in the feed →

Recurring issues are templates that materialize into a new issue on their own every so often: daily reviews, weekly reports, monthly maintenance.

What it is

Managed in Settings → Recurring. Each recurring item defines a template, a destination and a cadence, and can be paused and resumed.

How it’s defined

  • Template: title (required), description (optional) and priority.
  • Destination: the team and project where the issue will be born.
  • Cadence: daily, weekly or monthly, plus the date of the first run.

How to use it

Once created, Hilbana creates the issue for you when the date arrives and schedules the next one. You can pause a recurring item (it stops generating) and resume it whenever you want.

Details

  • The generated issue is born in the team’s first state (by order); the initial state isn’t configured in the template.
  • Each sweep generates at most one issue per recurring item; if it fell behind due to downtime, it catches up gradually.
  • Creating the issue and advancing to the next date happen together, with no duplicates.

Related: Issues · Workflow states · Automations.