- Home
- Skills
- 01000001 01001110
- Agent Jira Skills
- Jira Projects
jira-projects_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-projects- SKILL.md5.4 KB
Overview
This skill manages Jira Cloud projects for common project-level operations. It lists projects, fetches project configuration, and retrieves issue types, components, and versions via the Jira REST API. It is designed to be used with an authenticated JiraClient in Node.js or Python scripts.
How this skill works
The skill wraps Jira Projects endpoints and returns typed objects for projects, issue types, components, and versions. Functions build query parameters (expand, status, pagination) and call the JiraClient.request method to fetch API responses. Responses are normalized to arrays of domain objects and handle common options like expand and status filters.
When to use it
- List all accessible projects or page through large result sets
- Inspect a project’s configuration or expanded fields (description, lead, permissions)
- Retrieve available issue types for a specific project
- Fetch project components to populate dropdowns or validate component names
- List project versions for release planning or automation pipelines
Best practices
- Pass project key or numeric ID rather than project name to avoid ambiguity
- Use expand parameters (issueTypes, description, permissions) only when needed to reduce payload size
- Handle pagination when listing projects (startAt, maxResults) to support large instances
- Respect project browse permissions; ensure the JiraClient is authenticated with sufficient scopes
- Filter by status (LIVE, ARCHIVED, DELETED) or version status (UNRELEASED, RELEASED, ARCHIVED) to avoid stale data
Example use cases
- Display a searchable project list in an internal dashboard with avatars and descriptions
- Automate CI/CD release flows by retrieving project versions and marking releases
- Pre-populate issue creation forms with valid components and issue types for a project
- Validate user-entered project keys and return project metadata for integrations
- Generate a report of active projects and their leads for administration
FAQ
Pass the project key or numeric ID. Project names are not guaranteed unique and may cause errors.
How do I include issue types or description in the project details?
Use the expand option (e.g., expand=issueTypes,description) to request those fields when calling the get project endpoint.