# Atlassian MCP in Jira

**URL:** <https://forum.katalon.com/t/atlassian-mcp-in-jira/189104>\
**Category:** Web Testing\
**Tags:** integrations, web-testing\
**Created:** [March 16, 2026, 10:59am UTC](https://forum.katalon.com/t/atlassian-mcp-in-jira/189104 "2026-03-16T10:59:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevio052002](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/stevio052002/32/33213_2.png) [@stevio052002](https://forum.katalon.com/u/stevio052002)\
**Post date:** [March 16, 2026, 10:59am UTC](https://forum.katalon.com/t/atlassian-mcp-in-jira/189104/1 "2026-03-16T10:59:27Z")

</div>

How can we use Atlassian Jira automation rules to automatically update the status of a parent User Story based on the pass/fail results of linked automation test sub-tasks from the MCP Server?

Can this Generate and Auto-update the Status on the Local Device using the Auto-rule in Jira like Trigger and Condition

---

<div class="post-metadata">

**Author:** ![dineshh](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/dineshh/32/24488_2.png) [@dineshh](https://forum.katalon.com/u/dineshh)\
**Post date:** [March 16, 2026, 7:01pm UTC](https://forum.katalon.com/t/atlassian-mcp-in-jira/189104/2 "2026-03-16T19:01:44Z")

</div>

Use **Jira Automation Rules** with **Katalon TestOps integration** or **Katalon Jira app** to push test results (pass/fail) to sub-tasks, triggering parent User Story status updates—no direct MCP for rules, but API/webhooks bridge it.​

## Setup

1. Install **Katalon Test Automation for Jira** (Marketplace) → Link TestOps/Test Cases to Jira issues/sub-tasks.
2. **TestOps \> Integration \> Jira** → Map results to status (e.g., Pass → “Done”, Fail → “To Do”).
3. **Jira Automation Rule** :

- **Trigger** : Issue Updated (sub-task status changes).
- **Condition** : Test result = PASS (from custom field).
- **Action** : Edit parent Story → Transition to “Done”.

**Local Device** : Run tests → TestOps syncs results → Jira rule fires instantly (no manual). MCP aids StudioAssist for querying during dev, not runtime rules.​
