Skip to main content
Glama

set_issue_schedule

Add a recurring issue to a project, or change the one named by 'id' — the WHOLE of it as you write it here: what you leave out of a change is cleared, not kept. From 'nextDay' on, every 'every' weeks or months, the project files this issue at nine in the morning on YOUR clock and in YOUR name: with your access, through the same rules, notifications and watchers as an issue you filed yourself. In 'summary', {date}, {month}, {quarter} and {year} are read off the day it is filed ('VAT return {quarter}' → 'VAT return Q4 2026'). If the one filed before is still open, the new one is filed all the same and linked to it. A day missed — a paused project — files once when it can, never a backlog. Refused, with the reason, if the issue could not be filed as described today (an unknown type, an assignee nobody has). The project's lead, the company's owner or an admin only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe schedule to change, as list_issue_schedules returned it. Leave out to add one.
typeNoIssue type name, one of the project's. 'Task' where nothing is said.
unitNo'month' (the default) or 'week'.month
everyNoEvery how many units: 1 (the default), 3 for a quarter, 12 for a year. Up to 52 weeks or 24 months.
labelsNoLabels as 'a,b'.
enabledNofalse to keep it switched off. Default true.
nextDayYesThe first day it files on, YYYY-MM-DD, today or later on your clock. For months, its day of the month is the day kept (the 31st is a short month's last day).
projectYesThe project key, e.g. PM.
summaryYesThe filed issue's title; {date}, {month}, {quarter}, {year} are filled in on the day.
assigneeNoAssignee username or e-mail. Nobody where nothing is said.
priorityNoPriority name, e.g. 'High'.
dueInDaysNoThe filed issue's due day, as a number of days after the day it is filed — 19 makes an issue filed on the 1st due on the 20th. A count, not a day of the month. Leave out for no due day.
descriptionNoThe filed issue's description, Markdown; [~username] mentions notify each time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources