> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI for engineering and IT: stale work, follow-ups and access

> How engineering and IT teams use Hive with GitHub, Jira, Linear, Sentry and Slack to catch stale assigned work, turn meetings into tasks and keep changes approved.

Engineering work slips in quiet ways: an issue assigned months ago that nobody closed, action items from a planning meeting that never became tickets, a Sentry issue nobody picked up. Hive watches the tools your team works in, raises what's gone stale, and turns loose ends into proposed tickets and messages a person approves.

## The problems Hive solves

* **Assigned work goes stale** because priorities moved and the issue didn't.
* **Meeting actions evaporate** because nobody writes them into Jira.
* **Context lives in five tools** (GitHub, Jira, Slack, Sentry, docs), so answering a simple status question takes a search in each one.
* **Internal tools and APIs** don't have a ready-made connector.

## What Hive catches

| Signal | Source | What it means |
| - | - | - |
| Stale assigned work | GitHub | An open issue or pull request assigned to you hasn't been updated in 14 days. |
| Stale assigned work | Jira | An open issue assigned to you hasn't been updated in 14 days. |
| Unusual movement | Any connected tool | A metric Hive monitors, such as open issues or error counts, moved well outside its usual range. |
| Custom events | Incoming webhook or MCP server | Signed events or read-only counts from your own systems. |

<Note>
  The GitHub and Jira stale-work signals are switched on per workspace. Ask [support](/help/support) if you'd like them. Hive reads at most 5,000 assigned items per run.
</Note>

## Meetings into tickets

The **Meeting to Tasks** template starts from a short form where you paste a meeting transcript, give the Jira project key for the new issues, and give an email address for the recap:

```mermaid theme={null}
flowchart LR
  A[Form: meeting finished] --> B[Agent: extract tasks]
  B --> C[Loop: for each task]
  C --> D[Jira: create issue]
  B --> E[Outlook: draft follow-up]
```

Each Jira issue goes through the approval gate: writes to a connected tool, such as creating a Jira issue, wait for a person to approve them whatever the autonomy setting. See [Workflow templates](/workflows/templates) and [Autonomy and blast radius](/approvals/autonomy-and-blast-radius).

## Actions Hive can propose

With autonomy set to **Draft**, Hive can propose engineering changes for approval:

* **GitHub:** create, comment on, update, close or reopen issues, and add labels.
* **Jira:** create, comment on, assign, transition, update or label issues.
* **Sentry** (through its MCP server or connector): assign, comment on, resolve or ignore issues.
* **Slack:** post a message or reply in a thread.

Deleting a Jira issue is permanent, so it's treated as irreversible and always asks first. Every change leaves a receipt in the [audit log](/approvals/audit-log).

## Merged-PR summaries in Slack

Hive can post a summary of merged pull requests from selected GitHub repositories to a Slack channel. It posts through the configuring member's own Slack connection, so updates reach the team without anyone writing release notes by hand.

## Bring your own systems

* **MCP servers.** Connect any Model Context Protocol server over HTTPS, including the official Linear, Sentry, Notion and Stripe servers. Tools are pinned when you connect, so a server can't quietly change them later. Every tool is treated as high-risk until an operator says otherwise. See [MCP servers](/integrations/mcp-servers).
* **Incoming webhooks.** Send HMAC-signed JSON events from CI, monitoring or internal tools. See [Incoming webhooks](/integrations/incoming-webhooks) and [Webhook signing](/developers/webhook-signing).

## Ask Hive for status

* *What's assigned to me in Jira and GitHub that hasn't moved in two weeks?*
* *Summarise open pull requests in the payments repo.*
* *Which Sentry issues in the web project are unresolved and assigned to nobody?*
* *Draft a Slack update for #eng on what shipped this week.*

## For IT

* **Access reviews.** Okta can suspend a user, which Hive treats as a revoke-access action (B4, highest risk). It always needs approval and can be reversed by unsuspending.
* **Workspace control.** Admins decide which connectors members can use, see which accounts are connected (metadata only), and can stop everything with the [kill switch](/admin/safety-and-control).
* **Security posture.** Read the [security overview](/security/overview) and [data protection](/security/data-protection).

## Related

<CardGroup cols={2}>
  <Card title="Work and engineering integrations" icon="code-branch" href="/integrations/work-and-engineering">
    GitHub, Jira, Linear, Sentry, Trello and more.
  </Card>

  <Card title="Developers" icon="terminal" href="/developers/overview">
    Webhooks, public forms and how Hive works.
  </Card>
</CardGroup>

<Card title="Connect GitHub and Jira" icon="arrow-right" href="https://app.get-hive.ai">
  Start a 14-day trial with no card required. Connect read-only and see what's stale.
</Card>