Developer/draft-approve

Jira

Review Jira issues, projects, boards, sprints, and escalation work.

Install level

both

Jira setup needs your Atlassian site URL, account email, and one API token.

What It Does

Summarize sprint state, create issue drafts, update tickets after approval, and connect support escalations to engineering work.

Demo Scenario

Convert support themes into Jira issue drafts with priority and acceptance criteria.

API Reference

PageLines uses the provider's live API documentation as the source of truth for available actions, schemas, and version details.

View API docs

Sample conversation

user

What Jira work should engineering know about before standup?

agent

I reviewed Jira issues and grouped the standup-relevant work. I would review these draft updates before changing issue state.

| Issue | Status | Signal | Draft update |
|---|---|---|---|
| ENG-142 | In Progress | Blocked on sign-in callback test | Ask for reviewer and attach failing trace |
| ENG-151 | To Do | Three support tickets mention same bug | Raise priority and link Zendesk tickets |
| ENG-139 | Done | Needs release note | Draft customer-facing summary |