Help
Recurring Work Items copies a work item on a schedule, with its child tasks, into the right sprint. The work item you start from is the template; every copy is a new work item.
Get started
- Install the extension in your Azure DevOps organization from the Visual Studio Marketplace.
- Connect once. Open Boards → Recurring and select Connect. Copies are created with that Microsoft sign-in, so they appear on time even when nobody is online. One connection covers the whole organization.
- Make a work item recurring. Open it, select ⋯ → Make recurring, pick a schedule and select Make recurring.
It works with Azure DevOps Services organizations connected to Microsoft Entra ID. If yours isn't, the Recurring page says so.
Pick a schedule
| Repeat | Options |
|---|---|
| Daily | Every day, every few days, or every weekday |
| Weekly | Every week or every few weeks, on the days you pick |
| Monthly | On a date (the 1st) or a weekday (the second Tuesday, the last Friday); every 3 months reads as quarterly |
| Yearly | On a month and day |
| Every sprint | On the first or the last day of each sprint, from your team's sprint dates |
| After the last one is closed | A set number of days after the previous copy is closed |
Starts sets the first date and the time of day the copy is created, in your time zone. Upcoming shows the next three dates, the sprint and the assignee before you save.
Which sprint a copy lands in
- Current sprint: the sprint running on the day the copy is created.
- Next sprint: the one after it.
- Same as this item: the original's sprint, unchanged.
Every-sprint schedules always land in the sprint they belong to. If no future sprint exists yet, the schedule waits and checks again until one is added.
Who gets each copy
- Same as this item: the original's assignee.
- Take turns: add people from the project's teams, or anyone in the organization with Someone else…; each copy goes to the next person. The list shows who is next.
What each copy carries
The original's fields, tags, area and parent link. Its own copy of the child tasks, linked under it (on by default; turn off Gets its own copy of the child tasks). Optionally the date in its title. Each copy starts in its first state, without the original's history, dates or comments.
If the last one is still open: Skip this time (the history shows which item was still open) or Create a new one anyway.
Manage schedules
Boards → Recurring lists the project's schedules, with its next date, next assignee and last copy. The row menu has Create one now, Skip the next one, Pause / Resume, Edit schedule and Open work item. Select a row for its history. On the work item, the Recurring group shows the schedule, and ⋯ → Edit schedule changes or stops it.
Who can do what
- Anyone in the organization who can open the project sees its schedules and history.
- Setting up, changing, pausing or running a schedule needs permission to edit work items in that project.
- People outside the organization can't use the extension, even on public projects.
When a copy isn't created
- The original was deleted or moved: the schedule pauses, and the row says so. Stop it from the row menu.
- The assignee can't be assigned in the project any more: the schedule pauses and names the person. Edit the rotation, then resume.
- Azure DevOps was briefly unavailable: the run is retried every 15 minutes.
- The connection stopped working (the person who connected left, or their sign-in was revoked): the Recurring page shows Reconnect.
Support
Use crosstowntech.com/support, or the Support link on the Recurring page. What the extension reads and stores: Privacy & security.