bulk-ingestion

Batch ingest Jira tickets from a board or filter URL with deduplication and contradiction detection.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill bulk-ingestion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bulk-ingestion
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/herold/skills/bulk-ingestion
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill bulk-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of ingesting multiple Jira tickets from a board or filter, saving significant manual effort and ensuring all relevant tasks are captured.

Core Features & Use Cases

  • Batch Ticket Ingestion: Fetches all assigned, non-closed tickets from a specified Jira board or filter URL.
  • Deduplication: Intelligently skips tickets that have already been ingested locally within the last 24 hours.
  • Contradiction Detection: Automatically runs a contradiction detection check on each newly ingested ticket.
  • Use Case: A project manager needs to quickly bring all open tasks for the current sprint into the local development environment for review. They provide a Jira board URL, and the skill ingests all relevant tickets, flagging any potential requirement conflicts.

Quick Start

Use the bulk-ingestion skill to ingest all assigned tickets from the Jira board at https://hjemmesidekongen.atlassian.net/jira/software/projects/AI/boards/123.

Frequently Asked Questions about bulk-ingestion

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

FAQPage Schema
How do I ingest Jira tickets in bulk from a specific board?

To ingest Jira tickets in bulk, you provide a Jira board or filter URL, and the skill fetches all assigned, non-closed tickets from that board. It automatically writes a summary of the ingestion process after completion.

How does batch ingestion handle duplicate Jira tickets?

Batch ingestion handles duplicate Jira tickets by intelligently skipping any tickets that have already been ingested locally within the last 24 hours. This deduplication ensures only new tasks are processed.

Do I need the Atlassian MCP server to batch fetch Jira tickets?

Yes, batch fetching Jira tickets requires the Atlassian MCP server to access your board data. If the server is unavailable, the skill gracefully falls back to a message instead of failing.

Does the bulk ingestion process check for requirement conflicts?

Yes, the bulk ingestion process automatically runs a contradiction detection check on each newly fetched Jira ticket. This flags any potential requirement conflicts within the ingested tasks.

What limitations exist when importing Jira tickets in bulk?

When importing Jira tickets in bulk, a limitation is that deduplication only skips tickets ingested locally within the last 24 hours. Additionally, the process depends entirely on the Atlassian MCP server being available.