Skip to main content

Redmine

@webframp/redminev2026.11.03.1· Apache-2.0· 17d agoBEHAVIORS
01README

Redmine issue tracker integration — workflow-agnostic CRUD model.

Provides 28 model methods covering issues, projects, statuses, trackers, users, custom fields, relations, versions, time entries, watchers, search, issue categories, journal editing, file uploads, and attachment listing and download. Designed as composable primitives for building any workflow on top of Redmine.

For opinionated Kanban workflows, flow metrics, and sprint reports, see @webframp/redmine-kanban.

Quick Start

swamp extension pull @webframp/redmine
swamp vault create local_encryption redmine   # once, if you have no vault yet
swamp vault put redmine API_KEY               # prompts; never pass the key inline
swamp model create @webframp/redmine tracker \
  --global-arg host=https://your-redmine.example.org \
  --global-arg 'apiKey=${{ vault.get("redmine", "API_KEY") }}' \
  --global-arg project=your-project

The project global arg is now optional. Omit it for cross-project queries (e.g. list_issues with assignedToId: "me" across all projects). Methods that require a project (list_users, create_issue, list_versions, create_version, list_issue_categories) throw a clear error if none is provided.

02Release Notes

2026.11.03.1

Changed: Bump zod 4.6.5 → 4.6.7

2026.10.21.1

Changed: Documentation only: the README and the registry Quick Start now store the Redmine API key in a swamp vault (swamp vault put redmine API_KEY) and wire it with ${{ vault.get("redmine", "API_KEY") }}. The earlier examples passed apiKey=YOUR_API_KEY, which invited pasting the raw key onto the command line. The apiKey global argument description says the same.

Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade, so existing instances need no changes.

03Behaviors1
@webframp/redminev2026.11.03.1redmine/redmine.ts

Global Arguments

ArgumentTypeDescription
hoststringRedmine instance URL (e.g. https://redmine.example.com)
apiKeystringRedmine API key. Store it in a swamp vault and supply it as ${{ vault.get("redmine", "API_KEY") }}; never pass the literal key
project?stringDefault project identifier (omit for cross-project queries)
username?stringRedmine username for X-Redmine-Username header (required by some ingress configurations)
fn list_statuses()
List all issue statuses
fn list_trackers()
List all trackers
fn list_projects()
List all accessible projects
fn list_users(project?: string)
List project memberships (users and groups with their roles)
ArgumentTypeDescription
project?stringProject identifier (defaults to global project arg)
fn list_custom_fields()
List all custom field definitions
fn list_issues(project?: string, trackerId?: number, statusId?: union, assignedToId?: union, parentId?: number, limit?: number, sort?: string)
List issues matching filters
ArgumentTypeDescription
project?stringProject identifier
trackerId?numberFilter by tracker ID
statusId?unionFilter by status ID or open/closed/*
assignedToId?unionFilter by assignee ID or 'me'
parentId?numberFilter by parent issue ID
limit?numberMax results (default 100, max 500)
sort?stringSort field (e.g., 'updated_on:desc')
fn get_issue(issueId: number)
Get a single issue with journals and children
ArgumentTypeDescription
issueIdnumberIssue ID
fn create_issue(subject: string, project?: string, trackerId?: number, statusId?: number, priorityId?: number, assignedToId?: number, description?: string, parentIssueId?: number, estimatedHours?: number, customFields?: array)
Create a new issue
ArgumentTypeDescription
subjectstringIssue subject
project?stringProject identifier
trackerId?numberTracker ID
statusId?numberStatus ID
priorityId?numberPriority ID
assignedToId?numberAssignee user ID
description?stringIssue description
parentIssueId?numberParent issue ID
estimatedHours?numberEstimated hours
customFields?arrayCustom field values
fn update_issue(issueId: number, subject?: string, trackerId?: number, statusId?: number, priorityId?: number, assignedToId?: number, description?: string, parentIssueId?: number, estimatedHours?: number, doneRatio?: number, dueDate?: string, notes?: string, customFields?: array)
Update an existing issue
ArgumentTypeDescription
issueIdnumberIssue ID to update
subject?stringNew subject
trackerId?numberNew tracker ID
statusId?numberNew status ID
priorityId?numberNew priority ID
assignedToId?numberNew assignee user ID (null to unassign)
description?stringNew description
parentIssueId?numberNew parent issue ID
estimatedHours?numberNew estimated hours
doneRatio?numberPercent done (0-100)
dueDate?stringUpdated due date (YYYY-MM-DD)
notes?stringJournal note to add
customFields?arrayCustom field values to update
fn delete_issue(issueId: number)
Delete an issue
ArgumentTypeDescription
issueIdnumberIssue ID to delete
fn list_relations(issueId: number)
List relations for an issue
ArgumentTypeDescription
issueIdnumberIssue ID
fn create_relation(issueId: number, issueToId: number, relationType: enum, delay?: number)
Create a relation between two issues
ArgumentTypeDescription
issueIdnumberSource issue ID
issueToIdnumberTarget issue ID
relationTypeenumRelation type
delay?numberDelay in days (for precedes/follows)
fn delete_relation(relationId: number)
Delete a relation
ArgumentTypeDescription
relationIdnumberRelation ID to delete
fn list_versions(project?: string)
List project versions (milestones/sprints)
ArgumentTypeDescription
project?stringProject identifier (defaults to global project arg)
fn list_time_entries(issueId?: number, project?: string, userId?: number, from?: string, to?: string, limit?: number)
List time entries, optionally filtered by issue or project
ArgumentTypeDescription
issueId?numberFilter by issue ID
project?stringFilter by project identifier
userId?numberFilter by user ID
from?stringStart date (YYYY-MM-DD)
to?stringEnd date (YYYY-MM-DD)
limit?numberMax results (default 100, max 500)
fn log_time(issueId: number, hours: number, activityId?: number, comments?: string, spentOn?: string)
Log time spent on an issue
ArgumentTypeDescription
issueIdnumberIssue ID
hoursnumberHours spent
activityId?numberActivity ID
comments?stringComment
spentOn?stringDate spent (YYYY-MM-DD, defaults to today)
fn add_watcher(issueId: number, userId: number)
Add a watcher to an issue
ArgumentTypeDescription
issueIdnumberIssue ID
userIdnumberUser ID to add as watcher
fn remove_watcher(issueId: number, userId: number)
Remove a watcher from an issue
ArgumentTypeDescription
issueIdnumberIssue ID
userIdnumberUser ID to remove as watcher
fn search(query: string, project?: string, limit?: number)
Search across issues, projects, and wiki pages
ArgumentTypeDescription
querystringSearch query
project?stringScope search to project identifier
limit?numberMax results (default 25)
fn get_version(versionId: number)
Get a single version by ID
ArgumentTypeDescription
versionIdnumberVersion ID
fn create_version(project?: string, name: string, description?: string, status?: enum, dueDate?: string, sharing?: enum, wikiPageTitle?: string)
Create a project version (milestone/sprint)
ArgumentTypeDescription
project?stringProject identifier (defaults to global project arg)
namestringVersion name
description?stringDescription
status?enumVersion status
dueDate?stringDue date (YYYY-MM-DD)
sharing?enumSharing scope
wikiPageTitle?stringWiki page title
fn update_version(versionId: number, name?: string, description?: string, status?: enum, dueDate?: string, sharing?: enum, wikiPageTitle?: string)
Update a version
ArgumentTypeDescription
versionIdnumberVersion ID
name?stringNew name
description?stringNew description
status?enumNew status
dueDate?stringNew due date (YYYY-MM-DD)
sharing?enumNew sharing scope
wikiPageTitle?stringNew wiki page title
fn delete_version(versionId: number)
Delete a version
ArgumentTypeDescription
versionIdnumberVersion ID to delete
fn update_journal(journalId: number, notes: string, privateNotes?: boolean)
Update a journal entry's notes
ArgumentTypeDescription
journalIdnumberJournal ID
notesstringUpdated notes content
privateNotes?booleanMark notes as private
fn list_issue_categories(project?: string)
List issue categories for a project
ArgumentTypeDescription
project?stringProject identifier (defaults to global project arg)
fn upload_file(issueId: number, filePath: string, filename?: string, description?: string, contentType?: string)
Upload a file and attach it to an issue (two-step: upload binary, then attach token)
ArgumentTypeDescription
issueIdnumberIssue ID to attach the file to
filePathstringLocal file path to upload (relative to working directory)
filename?stringFilename for the attachment (defaults to basename of filePath)
description?stringAttachment description
contentType?stringMIME type (auto-detected from filename if omitted)
fn list_attachments(issueId: number)
List the attachments of an issue (ID, file name, size, content type, author, date). Read-only
ArgumentTypeDescription
issueIdnumberIssue ID
fn download_attachments(issueId: number, attachmentIds?: array, contentTypePrefix?: string, maxBytes?: number)
Download the attachments of an issue in one run (fan-out). Stores each file under the attachment file spec and writes the attachments resource listing every attachment with its data name and status. Filter by attachment IDs or a content-type prefix such as image/. Fails after writing the resource if any download failed. Read-only on Redmine
ArgumentTypeDescription
issueIdnumberIssue ID
attachmentIds?arrayOnly these attachment IDs (default: all)
contentTypePrefix?stringOnly attachments whose content type starts with this, e.g. image/ (case-insensitive)
maxBytes?numberSkip an attachment larger than this (default 20 MiB)

Resources

issues(30m)— List of issues matching query filters
issue_detail(30m)— Single issue with journals and children
projects(1h)— List of accessible projects
statuses(infinite)— Issue statuses (id, name, isClosed)
trackers(infinite)— Trackers (id, name, defaultStatus, description)
users(1h)— Project memberships (users and groups with roles)
custom_fields(infinite)— Custom field definitions (id, name, fieldFormat, possibleValues, ...)
relations(30m)— Issue relations (blocks, precedes, relates, etc.)
versions(1h)— Project versions (milestones/sprints)
time_entries(30m)— Time entries for issues or projects
search_results(15m)— Search results across issues, projects, and wiki
issue_categories(1h)— Issue categories for a project
attachments(1d)— Every attachment of one issue: ID, file name, size, content type, author, date,

Files

attachment(application/octet-stream)— Content of one issue attachment, named attachment-<issueId>-<attachmentId>
04Previous Versions19
2026.10.21.1Apache-2.0

2026.10.21.1

Changed: Documentation only: the README and the registry Quick Start now store the Redmine API key in a swamp vault (swamp vault put redmine API_KEY) and wire it with ${{ vault.get("redmine", "API_KEY") }}. The earlier examples passed apiKey=YOUR_API_KEY, which invited pasting the raw key onto the command line. The apiKey global argument description says the same.

Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade, so existing instances need no changes.

2026.10.20.2Apache-2.0

2026.10.20.2

Fixed: 2026.10.20.1 gave up on any Retry-After longer than 60 seconds. A rate limiter with a time window asks for up to the whole window: Skipper's clusterClientRatelimit over "2m", for example, sends up to about two minutes. So rate-limited calls failed where earlier versions waited. The cap is now 300 seconds, and it is also the total that all retries of one request may wait (so at most 5 minutes, not 4 × the cap). A longer Retry-After (a maintenance window, a daily quota) still fails fast instead of blocking the method.

Fixed: 2026.10.20.1 kept X-Redmine-API-Key and X-Redmine-Username on an http→https redirect to any port of the same host, so a TLS listener on an unexpected port received the key. Credentials now survive only the default upgrade, port 80 to 443, which is what a load balancer such as an AWS ALB issues. A setup that redirects elsewhere gets the set host to … error; set host to the https URL.

Fixed: A request with a streamed body was resent after a 307/308 redirect or a retryable status, though the first attempt had consumed the stream. A 307/308 now fails with a clear error, and a retryable status is returned at once instead of retried. No built-in method sends a streamed body.

Upgrade note: No schema or globalArguments changes; existing instances move to this version with an identity upgrade.

2026.10.20.1Apache-2.0

2026.10.20.1

Added: list_attachments lists the attachments of an issue (ID, file name, size, content type, author, date) into a new attachments resource, named attachments-<issueId>. download_attachments downloads them in one run into a new attachment file spec, named attachment-<issueId>-<attachmentId>. It filters by attachment IDs or a content-type prefix (case-insensitive) and skips files over maxBytes (default 20 MiB). Until now the type had no way to read an attachment.

The attachments resource always lists every attachment of the issue, with a status (listed after list_attachments; downloaded, not-selected, skipped-too-large or failed with an error after download_attachments) and, for downloaded ones, the dataName of the stored file. filter records the selection and maxBytes. The size limit applies to the bytes Redmine serves as well as to the size it records. A non-HTML attachment served as an HTML page (a login or proxy error page) is failed, not stored. If any download fails, the method stores the files that did download and the resource, then fails the run naming each failed attachment.

Fixed: Every request sent X-Redmine-API-Key and X-Redmine-Username to whatever host a redirect pointed at, because fetch strips only Authorization on a cross-origin redirect.

Fixed: Methods overwrote each other's stored data. Swamp stores data by name, not by spec. list_statuses, list_trackers, list_projects, list_custom_fields, and unfiltered list_issues and list_time_entries all wrote all. get_issue, create_issue, update_issue, list_relations, list_time_entries by issue, get_version and create_version wrote bare numeric IDs, and search wrote the bare sanitized query. list_users, list_versions, list_time_entries and list_issue_categories wrote the bare project. Within one method, list_time_entries ignored the user and date filters, and search mapped foo bar and foo-bar to the same name. Every data name now carries a spec prefix and every filter (see Upgrade note).

Fixed: The SPDX header in redmine.ts and its test said AGPL-3.0-or-later. Every source file now says Apache-2.0, matching LICENSE.md and the manifest.

Changed: A redirect to another origin now fails an API call with a message naming the URL to set as host. A same-origin redirect, or an http→https upgrade of the same host name on any port, still works. download_attachments follows other redirects without the credentials (S3 or CDN storage backends).

Changed: Only reads (GET) retry a 502, a 504 or a 503 without Retry-After. A gateway can time out after Redmine committed a write, so retrying created a duplicate issue or upload, added a second journal note, or reported a 404 for a delete that succeeded. Every method still retries a 429, and a 503 that carries Retry-After (a throttle rejecting before any work), unless the write was redirected. A Retry-After longer than 60 seconds is no longer slept on (it blocked the method for up to 4 × the value); the request fails instead. An HTTP-date Retry-After is now honored. upload_file's upload now uses the same retry and redirect handling as every other call.

Changed: list_time_entries rejects from and to values that are not real YYYY-MM-DD dates. Redmine ignored a malformed date and returned unfiltered entries.

Fixed: The limit descriptions of list_issues and list_time_entries said "default 25"; the default is 100, the maximum 500.

Changed: Requests no longer wait forever on a server that stops answering. JSON requests time out after 120 seconds per attempt, downloads after 60 seconds without data, and upload_file's upload after 10 minutes per attempt.

Upgrade note: Data names change. Update any data.latest(...) or model.<name>.resource.<spec>.<name> reference:

  • all → statuses-all, trackers-all, projects-all, custom-fields-all, issues-all, time-entries-all
  • <project> → users-<project>, versions-<project>, issue-categories-<project>
  • <filters> → issues-<filters>; <issueId> → issue-<issueId>, relations-<issueId>; <versionId> → version-<versionId>
  • time entries → time-entries-<filters> (e.g. time-entries-i:42, time-entries-p:web-u:3); search → search-<query>-<hash>

Data stored under the old names is not migrated; rerun the method to write it under the new name. No globalArguments changes.

Modified 1 behaviors

2026.10.14.1Apache-2.0(was none)

2026.10.14.1

Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.

Upgrade note: Metadata only. No code, schema, or behavioral changes.

2026.09.19.1

Fixed: redmineApi/redmineApiPaginated had no retry logic — any 429 (or 502/503/504) failed the request outright. A caller sequentially fetching many issues (e.g. an enrichment step iterating over a large ticket list) can trip Redmine's rate limiter even at concurrency 1, and every prior release turned that into a hard failure. Both helpers now retry through a shared fetchWithRetry, honoring Retry-After when the server sends one and falling back to exponential backoff (up to 4 retries) otherwise.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.19.1

2026.09.19.1

Fixed: redmineApi/redmineApiPaginated had no retry logic — any 429 (or 502/503/504) failed the request outright. A caller sequentially fetching many issues (e.g. an enrichment step iterating over a large ticket list) can trip Redmine's rate limiter even at concurrency 1, and every prior release turned that into a hard failure. Both helpers now retry through a shared fetchWithRetry, honoring Retry-After when the server sends one and falling back to exponential backoff (up to 4 retries) otherwise.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.18.1

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.15.1

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.28.1

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.3

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.1

2026.08.26.1

Fixed: Added missing description field to upgrade entry for version 2026.08.24.2. The omission caused swamp extension pull to fail with a catalog validation error ("upgrades.N.description: Invalid input: expected string, received undefined").

2026.08.25.1

2026.08.25.1

Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.

updated labels

2026.08.24.3

2026.08.24.3

Added: Output metadata attributes for observability.

  • durationMs: Method execution duration in milliseconds.
  • collectedBy: Extension name that produced the data.
  • fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2

2026.08.24.2

Added Troubleshooting section documenting 500-item pagination cap without truncated field, no retry/degradation, optional project requirement, update_issue re-fetch, upload_file path requirement, and reports/workflows living in separate extension.

2026.08.21.3

2026.08.21.3

Changed:

  • search now rejects an empty query with a clear validation error, instead of sending an empty search to Redmine and writing a resource under an empty instance name.
  • Redmine API and network-level errors now name the HTTP method and request path (e.g. "Redmine API GET /issues.json failed (500): ..."), instead of only the status code. A connection failure (DNS, refused, timeout) now names the method, path, and host instead of surfacing a bare fetch exception.
  • upload_file failures now name the file path and issue id when the file can't be read, and the filename, host, and issue id when the upload itself fails — instead of a bare "Upload failed: <status>" with no indication of what was being uploaded or to where.

2026.08.21.2

Changed: Tightened host and apiKey on the global-args schema, and subject on create_issue's argument schema, to require non-empty strings. All three are required identifiers/tokens that the Redmine API never accepts empty — this catches misconfiguration at model-create/method-call time instead of a confusing API failure.

2026.08.21.1

Added

  • Retroactive compatibility note for the list_issues resource instance-name change introduced in 2026.08.10.1.

Upgrade note (retroactive — applies to 2026.08.10.1)

Breaking change to list_issues data-resource instance names.

Prior to 2026.08.10.1, list_issues wrote its data resource under the constant instance name all. Starting with 2026.08.10.1 (PR #343 — make project global arg optional), the instance name is derived from active filters using a prefixed scheme to avoid collisions between hyphenated project identifiers and downstream field values:

Filter combination Old instance name New instance name
No filters all all (unchanged)
project only all p:<project>
project + parentId all p:<project>-parent:<parentId>
project + assignedToId all p:<project>-a:<assignedToId>

The table shows representative examples. All active filter arguments contribute segments in the order: p:, a:, s:, t:, parent:.

Impact: Any data.query expression or workflow step that references the list_issues resource by its old instance name will fail with an index-out-of-bounds error after upgrading past 2026.08.10.1.

Recommended consumer pattern: Within workflows, prefer filtering on workflowRunId rather than name when querying list_issues output. The workflowRunId predicate is stable across filter and naming changes:

data.query("tracker", "issues", workflowRunId == run.id)

2026.08.20.1

Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.

2026.08.21.2

2026.08.21.2

Changed: Tightened host and apiKey on the global-args schema, and subject on create_issue's argument schema, to require non-empty strings. All three are required identifiers/tokens that the Redmine API never accepts empty — this catches misconfiguration at model-create/method-call time instead of a confusing API failure.

2026.08.21.1

Added

  • Retroactive compatibility note for the list_issues resource instance-name change introduced in 2026.08.10.1.

Upgrade note (retroactive — applies to 2026.08.10.1)

Breaking change to list_issues data-resource instance names.

Prior to 2026.08.10.1, list_issues wrote its data resource under the constant instance name all. Starting with 2026.08.10.1 (PR #343 — make project global arg optional), the instance name is derived from active filters using a prefixed scheme to avoid collisions between hyphenated project identifiers and downstream field values:

Filter combination Old instance name New instance name
No filters all all (unchanged)
project only all p:<project>
project + parentId all p:<project>-parent:<parentId>
project + assignedToId all p:<project>-a:<assignedToId>

The table shows representative examples. All active filter arguments contribute segments in the order: p:, a:, s:, t:, parent:.

Impact: Any data.query expression or workflow step that references the list_issues resource by its old instance name will fail with an index-out-of-bounds error after upgrading past 2026.08.10.1.

Recommended consumer pattern: Within workflows, prefer filtering on workflowRunId rather than name when querying list_issues output. The workflowRunId predicate is stable across filter and naming changes:

data.query("tracker", "issues", workflowRunId == run.id)

2026.08.20.1

Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.

2026.08.21.1

2026.08.21.1

Added

  • Retroactive compatibility note for the list_issues resource instance-name change introduced in 2026.08.14.1.

Upgrade note (retroactive — applies to 2026.08.14.1)

Breaking change to list_issues data-resource instance names.

Prior to 2026.08.14.1, list_issues wrote its data resource under the instance name all (or all-<parentId> when a parent filter was active). Starting with 2026.08.14.1, the instance name is derived from active filters using a prefixed scheme to avoid collisions between hyphenated project identifiers and downstream field values:

Filter combination Old instance name New instance name
No filters all all (unchanged)
project only all p:<project>
project + parentId all-<parentId> p:<project>-parent:<parentId>
project + assignedToId all p:<project>-a:<assignedToId>

The table shows representative examples. All active filter arguments contribute segments in the order: p:, a:, s:, t:, parent:.

Impact: Any data.query expression or workflow step that references the list_issues resource by its old instance name will fail with an index-out-of-bounds error after upgrading past 2026.08.14.1.

Recommended consumer pattern: Within workflows, prefer filtering on workflowRunId rather than name when querying list_issues output. The workflowRunId predicate is stable across filter and naming changes:

data.query("tracker", "issues", workflowRunId == run.id)

2026.08.20.1

Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.

2026.08.20.1

2026.08.20.1

Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.

2026.08.14.1

2026.08.10.1

Changed: The project global argument is now optional. This enables cross-project queries — most notably list_issues with assignedToId: "me" across all accessible projects, equivalent to Redmine's /my/page view.

  • list_issues and search operate across all projects when no project is specified (neither as a method argument nor globally).
  • Methods that require a project in their URL path (list_users, create_issue, list_versions, create_version, list_issue_categories) throw a clear error if none is resolved from either source.
  • Instance names for list_issues now include all active filter fields with prefixes (p:, a:, s:, t:, parent:) to prevent cache collisions between different filter combinations.

Upgrade: Existing model instances with project set continue to work unchanged. The upgrade is a no-op identity function (no persisted data migration needed). New instances may omit project for cross-project queries.

2026.07.18.1

Added: An upgrades array entry (no-op) to redmine.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.

2026.07.09.1

Fixed: Extension failed to load with Last upgrade toVersion "2026.06.21.1" does not match model version "2026.07.08.1" for model type "@webframp/redmine". #194 bumped the model's version field to match the manifest but never added a matching upgrades entry, leaving the upgrade chain one version short of the declared model version — a rule the registry enforces at load time. This adds the missing no-op upgrade entry and bumps the version again so the chain is complete. No behaviour change beyond #194.

2026.08.10.1

2026.08.10.1

Changed: The project global argument is now optional. This enables cross-project queries — most notably list_issues with assignedToId: "me" across all accessible projects, equivalent to Redmine's /my/page view.

  • list_issues and search operate across all projects when no project is specified (neither as a method argument nor globally).
  • Methods that require a project in their URL path (list_users, create_issue, list_versions, create_version, list_issue_categories) throw a clear error if none is resolved from either source.
  • Instance names for list_issues now include all active filter fields with prefixes (p:, a:, s:, t:, parent:) to prevent cache collisions between different filter combinations.

Upgrade: Existing model instances with project set continue to work unchanged. The upgrade is a no-op identity function (no persisted data migration needed). New instances may omit project for cross-project queries.

2026.07.18.1

Added: An upgrades array entry (no-op) to redmine.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.

2026.07.09.1

Fixed: Extension failed to load with Last upgrade toVersion "2026.06.21.1" does not match model version "2026.07.08.1" for model type "@webframp/redmine". #194 bumped the model's version field to match the manifest but never added a matching upgrades entry, leaving the upgrade chain one version short of the declared model version — a rule the registry enforces at load time. This adds the missing no-op upgrade entry and bumps the version again so the chain is complete. No behaviour change beyond #194.

05Stats
A
100 / 100
Downloads
283
Archive size
41.5 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License2/2earned
  • Verified public repository2/2earned
06Platforms
07Labels