jira-agile_skill
- JavaScript
3
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill 01000001-01001110/agent-jira-skills --skill jira-agile- SKILL.md6.9 KB
Overview
This skill manages Jira Agile boards and sprints for Jira Cloud. It provides functions to list Scrum/Kanban boards, create and transition sprints, and move issues into or out of sprints using the /rest/agile/1.0/ endpoints. It’s implemented as a small extension to an authenticated Jira client for Node.js/TypeScript environments.
How this skill works
The skill extends a base JiraClient with an agileRequest helper that targets /rest/agile/1.0. It exposes operations to list boards, fetch board sprints, get sprint issues, create sprints, start/end sprints, and post issue moves into sprints. Each operation calls the Agile REST endpoints and returns typed JSON objects or throws descriptive errors on non-2xx responses.
When to use it
- When you need to list Scrum or Kanban boards programmatically.
- When you need to create, start, or close sprints from automation scripts.
- When you need to move issues into a sprint or reorder issues within a sprint.
- When you need to fetch issues assigned to a specific sprint for reports or sync.
- When building CLI or cross-platform scripts (Node.js / Python wrappers) for sprint management.
Best practices
- Authenticate using a JiraClient with proper credentials and scopes before calling Agile endpoints.
- Always use /rest/agile/1.0/ for board/sprint operations (not /rest/api/3/).
- Check board type: Kanban boards do not support sprints.
- Avoid adding issues to closed sprints and validate sprint state first.
- Paginate results when listing boards or sprint issues using startAt/maxResults.
Example use cases
- List all Scrum boards for a project to let users pick where to create a sprint.
- Create a new sprint with start/end dates and a goal, then move selected issues into it.
- Start a sprint programmatically at a scheduled time and set its endDate.
- Fetch all issues in an active sprint to generate a progress report or export.
- Reorder or batch-move issues into a sprint after a planning session.
FAQ
You can list Kanban boards, but Kanban boards do not support sprints, so sprint-related calls are not applicable.
What happens if I try to add issues to a closed sprint?
The Jira Agile API rejects adding issues to closed sprints. Validate the sprint state and open it before moving issues.