S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

jira-commands

Automação Autor: mulhamna

Change a Jira issue to another issue type using Jira's native move semantics with jirac

42estrelas
Atualizado há 3 meses
Ver no GitHub ↗ Licença: NOASSERTION

Como adicionar

/plugin marketplace add mulhamna/jira-commands

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/jira-commands-mrdggp84/svg)](https://www.skillteca.com.br/skills/jira-commands-mrdggp84)

Skills relacionadas

Ver todas de Automação →

MoneyPrinterTurbo

90.3k

利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.

Automação por harry0703

weather-svg-creator

58.4k

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

Automação #ai por shanraisshan

asana-automation

41.2k

Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.

Automação #git #github por sickn33

payment-integration

41.2k

Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.

Automação #git #github por sickn33

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Change an issue's type (e.g. Bug → Story) using jirac. This uses Jira's native move semantics — the issue key is preserved.

Steps:

  1. Check that jirac is available by running jirac --version. If missing, tell the user to install it (cargo install jira-commands).
  2. Extract from the user's request:
  3. issue key
  4. target issue type name (e.g. Bug, Story, Task, Sub-task)
  5. Confirm intent — type changes can affect required fields and screens.
  6. Run jirac issue change-type <KEY> <TYPE>.
  7. Report the updated issue and its new type. Use jirac issue view <KEY> if confirmation is needed.

Notes:

  • Issue key is preserved (PROJ-123 stays PROJ-123).
  • Some custom-field values may be dropped if the new type's screen excludes them — verify with jirac issue fields -p PROJ --issue-type <TYPE> beforehand.
  • Use jirac issue move instead when moving across projects; use change-type when staying in the same project.

Examples:

  • "change PROJ-123 to a Bug" → jirac issue change-type PROJ-123 Bug
  • "convert PROJ-50 from Sub-task to Story" → jirac issue change-type PROJ-50 Story
Compartilhar X LinkedIn