jira-task

$npx mdskill add liferay/liferay-portal/jira-task

Creates a Jira task in the LPD project via REST API.

  • Solves creating a Jira task or LPD ticket from a commit or description.
  • Depends on Bash with curl and git, plus Glob, Grep, Read tools.
  • Infers task from commit hash or uses user-provided description.
  • Returns the ticket key and browse URL after creation.

SKILL.md

.github/skills/jira-taskView on GitHub ↗
---

allowed-tools: Bash(curl *), Bash(git *), Glob, Grep, Read
argument-hint: "[commit hash or description]"
description: Create a Jira task in the LPD project through the REST API. Use when the user asks to create a Jira task or LPD task ticket.
name: jira-task

---

# Create a Jira Task in LPD

Create a task ticket in the LPD Jira project through the REST API.

## Input

When `${ARGUMENTS}` is a commit hash, inspect the commit with `git show` to understand the work and infer the task. When `${ARGUMENTS}` is a free-form description, use it directly.

## Gather Information

Request any missing details from the user:

- **Summary** — short title describing the task.
- **Description** — what needs to be done and why.

## Required Fields

The LPD project requires the following fields. Apply these defaults unless the user specifies otherwise:

- **Component**: Infer from the code area. Fetch the LPD project components and select the one whose name matches the relevant area or keyword.
- **Issue Type**: `Task` (ID: `10002`).

Note: Unlike bugs, tasks do not require the Affects Version or Cross Cutting Properties fields.

## Create the Ticket

Create the issue in the LPD project with the gathered summary, description, and required fields. Author the description in Atlassian Document Format (ADF) with the following sections, in order: Description, Acceptance Criteria (when applicable). Append a Reference section when a commit is referenced.

## Output

The ticket key and the browse URL: `https://liferay.atlassian.net/browse/<KEY>`.

More from liferay/liferay-portal

SkillDescription
format-sourceFormat source files to align with Liferay's coding standards.
format-source-add-ruleAdd a new rule to the format-source skill, derived from a Git commit.
jira-bugCreate a Jira bug ticket in the LPD project through the REST API. Use when the user asks to create or file a Jira bug or LPD ticket.
markdown-formatFormat a Markdown file to match Liferay conventions — frontmatter order, Title Case headings, braced shell variables, long-form CLI flags, and professional prose. Use when the user asks to format, clean up, polish, or copy-edit a Markdown file destined for the Liferay repository.
poshi-migrateMigrate a Liferay Poshi .testcase file to its modern test layer (Playwright, Jest, JUnit unit, Java integration). Routes each test to the right layer, consolidates compatible tests at write time, and follows existing Playwright patterns from a configurable reference folder. Use when the user asks to migrate, port, or convert a Poshi .testcase to Playwright, Jest, or JUnit.
poshi-shrinkShrink a Liferay component's Poshi test suite by merging overlapping tests. Use when the user asks to reduce, merge, or clean up Poshi tests for a @component-name.
prCreate a GitHub PR for the current branch. Use when the user asks to create a PR, send a PR, or invokes /pr.
pr-checkCheck that a PR is ready to be sent for review.
pr-check-publishComment a pr-check run on an existing GitHub PR with a marker the webhook parses to apply the commit status and label. Use after rerunning pr-check on an open PR.
test-fixResolve a single Liferay test failure end-to-end.