Integrations / Jira

GitHub updates, alongside your Jira work item. The result and the next step in context.

Bring the pull request timeline and rule results into Jira with the Warestack Forge app. Ask about the linked change in Rovo and choose which updates a chain writes to the work item.

Connect Jira Get started

Jira Cloud · select the projects Warestack can access.

JiraSearchCreateLH

For you

Recent

Starred

Apps

Plans

Spaces

Recent

ORB

More spaces

Recommended

Create a roadmap

Filters

Dashboards

Confluence

Loom

Assets

Teams

Goals

Projects

Spaces/ORB/Add epic/ORB-418

Batch mute rules by label

Web links

orbital/console-web #1182Connect your GitHub account

Warestack pull request status

WARESTACK

orbital/console-web #1182

ORB-418: Batch mute rules by label

Status updated 14 minutes ago · View generated 2 Oct 2026, 10:05 · 7c3e1a9

ResultFlagged

Rules11 Passed · 1 Flagged

ReviewChanges Requested · 3 Open Review Threads

Checks6/6 Passing

MergeWarestack Rules Are Informational

DeploymentNot Deployed

Other GitHub checks or branch protection may still prevent merge. Jira does not enforce merge.

Next action

Address the three open review threads, then request review from jmarchetti. Bot approvals do not count toward Require approvals by branch prefix.

Rule details

12/12 rule outcomes available for this revision

Evaluated 14 minutes ago · 2 Oct 2026, 10:05

Require approvals by branch prefixFlagged

Medium Severity

Reason: feat/ requires 2 human approvals; 1 counted.

Next action: Request additional human reviewers. Bot approvals do not count toward this rule.

Open rule

Require a linked ticketPassed

High Severity

Rule passed for this pull request revision.

Open rule

Detect pull request scope driftPassed

Medium Severity

Rule passed for this pull request revision. All 14 changed files relate to ORB-418.

Open rule

Require concise pull requestsPassed

Low Severity

Rule passed for this pull request revision. 612 lines changed; limit for console-web is 800.

Open rule

Rules run wherever they are enabled in Warestack Rules.

Recent activity

Re-review requested

Review requested · Warestack

2 Oct 2026, 14:49

Revision pushed

Pull request synchronized · GitHub

2 Oct 2026, 14:48

Changes requested

Review submitted · jmarchetti

2 Oct 2026, 10:05

Rules evaluated

Rules evaluated · Warestack rule engine

30 Sep 2026, 09:21

Checks passed

Checks passed · Warestack

30 Sep 2026, 09:21

Open

Showing 5 of 23 recent events. Open the Warestack activity tab for the full timeline.

Open pull requestView in WarestackManage rules in WarestackReload status

Activity

Show:AllCommentsHistoryWork logWarestack

Warestack14 minutes ago

Re-review requested on orbital/console-web #1182 · ORB-418: Batch mute rules by label

Revision 7c3e1a9 resolved 3 review threads. Warestack Rules: 11 passed · 1 flagged · informational.

https://github.com/orbital/console-web/pull/1182

In Progress

Details

AssigneePNPriya Nair

ParentAdd parent

SprintORB Sprint 42

PriorityMedium

Labelsalerts

Due dateAdd due date

TeamPlatform

Start dateSep 29, 2026

Story point estimate3

Fix versionsNone

ReporterLHLena Hartmann

Development

1 branch

2 commits

1 pull request OPEN

6 builds

AutomationRule executions

A Jira work item with the Warestack panel open. Sample data from a workspace.

Three things on every work item.

Each one is written as GitHub events happen, not assembled when someone opens the item.

Issue panel

The pull request timeline

Opened, standards checked, review requested, approved, merged, deployed. Each entry with who, when and the status word. Which events are written is decided per chain.

Beside the fields

The result and the next step

Passed, Would have failed or Not evaluated, with the standards count, approvals, deployment and whether the merge is blocked. Searchable with JQL once the result field is enabled.

Rovo

Answers on the work item

Ask the Warestack agent where a change stands and what to do next. It reads the work item and the linked pull request and shows its sources.

Ask the work item where it stands.

The Warestack agent in Rovo answers from the work item and the linked pull request: review state, standards passed and flagged, checks, deployment, and what to do next.

Grounded in the record. Answers come from Warestack data and the work item, with the sources shown. Nothing is guessed from the code.

Read-only in the first release. The agent reports and recommends. Re-requesting review or triggering a chain stays with the person.

Chat · Warestack · ORB-418Coming

What is the status of ORB-418 and what do we do next?

Read the work item and console-web #1182. In progress, waiting on the author.

Review. Changes requested by jmarchetti on Oct 2, three threads open.

Standards. 11 of 12 passed. One finding: feat/ requires 2 human approvals, 0 counted. Not blocking.

Next step. Address the three threads and re-request review from jmarchetti. Nothing blocks the merge.

Ask Warestack…

Standards that read the work item.

These rules use Jira as evidence. They run on the pull request, where the change can still be fixed.

Require a linked work item

Flags pull requests without a Jira work item in the branch name, title or body.

Catalog rule

Require the work item to be assigned

Flags pull requests whose linked work item has no assignee.

Catalog rule

Require an active work item

Flags pull requests whose linked work item is not in an In Progress status category.

Catalog rule

Detect scope drift

Flags pull requests whose changes do not match the linked work item’s description.

Catalog rule

Require acceptance criteria before assignment

Flags assigned work items whose description does not define verifiable acceptance criteria.

Catalog rule

Install in three steps.

A Jira admin installs the app and picks the projects. Warestack verifies it can read each one before anything is written.

Connect Jira Read the docs

Connect Jira from Warestack

Integrations → Connect Jira → choose the site. OAuth returns to Warestack.

Pick the projects

Select the Jira projects Warestack may read. Each one shows an evidence status and the reason if access is blocked.

Decide what is written

Chains choose which timeline events reach the work item. Rules start informational. Nothing blocks a merge until you require the check.

Review the requested permissions during connection. Select the projects Warestack can access and the timeline updates each chain writes.