| name | jira |
| description | Use for Jira work through the official Atlassian Rovo MCP Server. Prefer this skill for team Jira tasks, project lookup, issue search, issue creation, and project-specific workflow defaults. |
Jira
Use the official Atlassian Rovo MCP Server.
Defaults
- Site:
YOUR_ATLASSIAN_SITE_URL
- Cloud ID or site URL:
YOUR_ATLASSIAN_CLOUD_ID_OR_SITE_URL
- Primary Jira project key:
YOUR_DEFAULT_PROJECT_KEY
- Prefer JQL for issue-listing tasks.
- Ask before creating, editing, commenting on, or transitioning issues unless the user explicitly asks for that action.
Workflow
- For project discovery, use
getVisibleJiraProjects when the project key is unknown.
- For issue lists, use
searchJiraIssuesUsingJql with the default project key.
- For creating issues, use
getJiraIssueTypeMetaWithFields first when required fields are unknown.
- For status changes, use
getTransitionsForJiraIssue before transitionJiraIssue.
- For pull request, build, deployment, or repository context, use
getTeamworkGraphContext when available.
Guardrails
- Keep read-only requests read-only.
- Treat Codex hooks as workflow guardrails, not permission boundaries.
- Do not expose OAuth tokens, API tokens, or private cloud IDs in summaries.
- If the user asks for a write action and the project key is ambiguous, ask for confirmation.