jira-fields-and-flags

Sets Jira priority, due date, labels, and Flagged field on triaged legal tickets via Atlassian MCP.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill jira-fields-and-flags-mypostech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-fields-and-flags
Source: https://github.com/myPOStech/mps-legal-legalcopilot-ai/tree/main/skills/jira-fields-and-flags
Command: npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill jira-fields-and-flags-mypostech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legal triage outcomes like priority, SLA deadlines, and risk flags often end up buried in Jira comments where nobody can filter or sort on them. This Skill writes those values directly into native Jira fields so the team can actually act on them. ## Core Features & Use Cases - Native field updates: Sets Priority, Due date, Labels, and the Flagged (Impediment) field in a single atomic editJiraIssue call. - SLA-aware due dates: Computes due dates from SLA days, rolls weekend deadlines back to Friday, and never sets a date in the past. - Label merging and risk flags: Merges new matter/risk labels with existing ones and turns on the Impediment flag only for genuine blockers like regulator, claim, or inspection risks. - Use Case: After a legal-triage skill classifies ticket LEGAL-4321 as a high-priority NDA with a claim risk, this Skill sets priority=High, due date, labels matter:nda and risk:claim, and flags the ticket for lawyer attention. ## Quick Start Ask the assistant to run the jira-fields-and-flags skill on ticket LEGAL-4321 with priority High, a 7-day SLA, matter type nda, and a claim risk flag.

Frequently Asked Questions about jira-fields-and-flags

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

FAQPage Schema
How do I set Jira priority and due date via the Atlassian MCP?

Use mcp__atlassian__editJiraIssue with fields containing priority as {"name": value} and duedate as a YYYY-MM-DD string. This Skill computes the due date from SLA days, rolling weekend dates back to the previous Friday.

How to set the Jira Flagged Impediment field programmatically?

Set customfield_10021 to [{"value": "Impediment"}] to flag a ticket, or an empty array to clear it. If the field ID differs on your Jira instance, look it up once via getJiraIssueTypeMetaWithFields and cache it in knowledge/config.md.

Does updating Jira labels overwrite existing labels?

No. The Skill reads the current label set via getJiraIssue and merges new labels like matter:nda and risk:claim into it, so existing labels are never removed.

What happens if a Jira field edit is rejected?

The Skill peels off the unknown field and retries, prioritizing priority and duedate above flagged and labels. If priority or duedate cannot be set, it returns applied: false with the error reason instead of silently dropping them.

When should the Jira Impediment flag not be set?

Avoid flagging unless risk flags include regulator, inspection, or claim, human review is required, or the SLA is two days or less. Spurious flags train the team to ignore them.