AI agents that refine your Jira backlog and
open the pull request
Connect Jira to Agentopia by CynetIQ and let AI agents pick up issues, refine them with acceptance criteria and story points, route security tasks to the right agent based on reporter, and ship a PR on GitHub or Azure DevOps — with status transitions written back to Jira.
The flow, end to end
- 1Jira issue → Agentopia by CynetIQ taskAgentopia by CynetIQ polls Jira via JQL or webhook. Each matching issue becomes a Task with full description, acceptance criteria, attachments, and a backlink to the Jira ticket.
- 2Integration Rules tag and routeRules match on reporter, issue type, project, or label. Example: reporter = security@yourcompany.com → tag = security_review, agent = security_developer, priority = critical. Same rule engine works for Jira AND Azure DevOps.
- 3AI Refinement (optional)Click ✨ Refine on the task. The PM agent expands the description, writes acceptance criteria, estimates story points, and suggests an assignee based on prior expertise.
- 4AI pipeline runsanalyzer → planner → developer → reviewer. The reviewer agent runs an OWASP-aware code review against the diff and produces a severity + score.
- 5PR opened, Jira updatedA pull request is opened on GitHub or Azure DevOps. The Jira issue gets a comment with the PR URL, transitions to "In Review", and (when the PR merges) auto-transitions to "Done".
What you get out of the box
Setup in 5 minutes
- Create an Atlassian API token at
id.atlassian.com/manage-profile/security/api-tokens. - In Agentopia by CynetIQ → Integrations → Jira, paste your email + token + site URL (e.g.
yourco.atlassian.net). - Pick which Jira projects to sync and define a JQL filter (default:
resolution = Unresolved AND assignee = currentUser()). - Map each Jira project to a target repo (GitHub or Azure DevOps).
- Add an Integration Rule for security routing: reporter in (security-team) → agent = security_developer, tag = security_review, priority = critical.
Frequently asked
How does Agentopia by CynetIQ work with Jira?
Agentopia by CynetIQ imports Jira issues (via JQL filter or per-project sync), turns each into a Task, runs the AI agent pipeline (analyzer → planner → developer → reviewer), opens a PR on the linked GitHub or Azure DevOps repo, and writes back to the Jira issue with PR URL, status transitions, and refinement output (acceptance criteria, story points, suggested assignee).
Can I route security tickets to a different agent automatically?
Yes — define an Integration Rule that matches Jira reporter, issue type, project, or label. For example: reporter = security@yourcompany.com OR label = security → auto-tag = security_review, agent = security_developer, priority = critical. The same rule engine works for both Jira and Azure DevOps.
Does Agentopia by CynetIQ write story points back to Jira?
Yes — when you run AI Refinement on a Jira-sourced task, Agentopia by CynetIQ writes the estimated story points to the Jira custom field you configure (default: customfield_10016). Acceptance criteria and refined description are also written back as a Jira comment.
Which Jira authentication is supported?
API token via email + token (Atlassian Cloud) or PAT (Jira Server / Data Center). Stored encrypted server-side, scoped to the configured site URL. Agentopia by CynetIQ never reads code through Jira — only issue content.
Do I need Jira Premium or a specific Atlassian plan?
No — Agentopia by CynetIQ works with Jira Free, Standard, Premium, and Enterprise. Custom field IDs are auto-detected. JQL filters can be edited per project.
How is this different from Atlassian Intelligence?
Atlassian Intelligence summarises and rewrites issue text. Agentopia by CynetIQ actually writes the code, opens the PR, runs an AI code review, and resolves the Jira issue when the PR merges. They are complementary — many teams use both.
