Create and edit recurring Issues

Recurring schedules reuse the ordinary Issue fields and permission model. Integrity confirms every change on the server and keeps the current values visible while a save is pending.

Create a recurring Issue Admin Editor

1. Open the Issue create dialog for an active Team.
2. Enter the root Issue title and any supported Description, status, priority, assignee, Feature, Phase, labels, estimate, attachments, and direct sub-Issues.
3. Open the footer menu and select Make recurring.
4. Choose the first due date and a repeat interval from 1 through 12 days, weeks, months, or years.
5. Select Create recurring issue.

Integrity creates the schedule, its first immutable version, its first occurrence, and the first ordinary Issue in one transaction. Repeating a timed-out submission with the same request does not create a duplicate schedule or Issue.

Edit a schedule Admin Editor

1. Open the generated Issue's overflow menu and select Edit recurring issue, or open the schedule from Team settings → Recurring issues.
2. Change the next due date or repeat interval.
3. Review the calendar preview.
4. Select Save changes.

A meaningful save creates a new schedule version and affects future occurrences only. If another user saved first, Integrity rejects the stale edit and asks you to reload the current schedule.

Duplicate a schedule Admin Editor

Open a schedule in the Team recurring-Issue directory and select Duplicate. Integrity copies the current definition and timing into a new schedule, creates its first ordinary Issue, and assigns the duplicate a different stable schedule key.

The duplicate has independent future versions, occurrences, retries, and lifecycle state.

Align several schedules Admin Editor

1. Select generated Issues in a Team Issue table.
2. Open Actions → Edit recurring issues.
3. Review the applicable and inapplicable counts.
4. Choose one next due date and repeat interval.
5. Confirm the update.

Integrity deduplicates Issues that belong to the same schedule and applies the complete batch atomically. A stale or inaccessible schedule blocks the batch; no partial timing change remains.

Stop one schedule Admin Editor

Open the schedule editor or generated Issue menu, select Stop recurrence, and confirm the destructive action.

Stopping is idempotent. It prevents future generation and removes the schedule from the active directory without deleting generated Issues, versions, occurrence evidence, or Logs.

Stop several schedules Admin Editor

Select generated Issues, open Actions → Remove recurring for all, review the deduplicated schedule count, and confirm.

The command stops every applicable schedule atomically. It does not archive, delete, or change any generated Issue.

Related