jira-writer

Update JIRA issues on the Red Hat Issue Tracker via the JIRA API.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/redhat-documentation/redhat-docs-agent-tools --skill jira-writer-redhat-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-writer
Source: https://github.com/redhat-documentation/redhat-docs-agent-tools/tree/main/plugins/docs-tools/skills/jira-writer
Command: npx skills add https://github.com/redhat-documentation/redhat-docs-agent-tools --skill jira-writer-redhat-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira, ratelimit, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of updating JIRA issues, allowing for the efficient pushing of release notes, modification of custom fields, and status updates, thereby reducing manual effort and ensuring data consistency.

Core Features & Use Cases

  • Push Release Notes: Update the release note custom field with generated content.
  • Update Status: Set release note status to 'Proposed', 'Approved', or 'Rejected'.
  • Update Custom Fields: Modify any custom field on a JIRA issue.
  • Batch Updates: Update multiple issues with the same content simultaneously.
  • Use Case: After a feature is released, use this skill to push the release notes and set the status to 'Approved' for multiple JIRA tickets at once.

Quick Start

Use the jira-writer skill to update JIRA issue COO-1145 with the release note text "Fixed critical bug in user authentication module."

Frequently Asked Questions about jira-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update JIRA issues with release notes automatically?

To update JIRA issues with release notes automatically, you can use an automation workflow that pushes generated content to the release note custom field and modifies issue properties. This requires write operations that need user approval before execution.

Can I update custom fields on multiple JIRA tickets at once?

Yes, you can update custom fields on multiple JIRA tickets at once using batch update functionality. This allows you to push the same release note content and set statuses like 'Approved' or 'Proposed' across several issues simultaneously to ensure data consistency.

What is the best way to set the release note status in JIRA to Proposed or Rejected?

The best way to set the release note status in JIRA to 'Proposed', 'Approved', or 'Rejected' is through an issue tracking automation script. It directly modifies the custom status fields on the Red Hat Issue Tracker via API interaction.

Does the JIRA API support rate limiting for batch issue updates?

Yes, managing JIRA API rate limiting for batch issue updates is handled using the ratelimit Python package. This prevents API throttling when pushing release notes or modifying custom fields across multiple issues.

Do I need user approval to modify JIRA issue properties through automation?

Yes, you need user approval to modify JIRA issue properties through automation. Because the system performs write operations to update release notes and custom fields, it requires explicit user approval before executing any changes.