Skip to content

docs(#1992): add JIRA-driven workflows tracking issues to roadmap #2272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralphbean merged 1 commit into from
Jun 15, 2026
+6 −0
Merged

docs(#1992): add JIRA-driven workflows tracking issues to roadmap #2272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,12 @@ Examples of work that could move this forward:

With feature refinement establishing the pattern, extend agent capabilities deeper into project management — picking up stories, refining acceptance criteria, and linking implementation back to tracking. This extends fullsend's trigger model beyond forge events into project management systems.

Examples of work that could move this forward:

@fullsend-ai-review fullsend-ai-review Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[info] authorization-chain

The PR references seven newly filed tracking issues (#2263-#2269). These issues could not be verified via GitHub API, but the PR body claims they exist and the change structure matches the authorized scope exactly. Human reviewer should spot-check that the linked issues exist.


- JIRA trigger model ([#2263](https://github.com/fullsend-ai/fullsend/issues/2263))
- Per-agent JIRA support: triage ([#2264](https://github.com/fullsend-ai/fullsend/issues/2264)), code ([#2265](https://github.com/fullsend-ai/fullsend/issues/2265)), prioritize ([#2266](https://github.com/fullsend-ai/fullsend/issues/2266)), retro ([#2267](https://github.com/fullsend-ai/fullsend/issues/2267)), review ([#2268](https://github.com/fullsend-ai/fullsend/issues/2268)), refine ([#1341](https://github.com/fullsend-ai/fullsend/issues/1341))

@fullsend-ai-review fullsend-ai-review Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] Missing or stale documentation

The diff lists refine alongside five existing default agents (triage, code, prioritize, retro, review) in the Per-agent JIRA support line, but no refine agent currently exists as a harness definition or in docs/agents/README.md. However, refine appears to reference a planned capability and the roadmap Feature refinement section describes this as a future agent area.

Suggested fix: Consider adding a brief annotation (e.g., refine (planned)) to distinguish the not-yet-implemented agent from the five that already exist.

- JIRA identity and credential management ([#2269](https://github.com/fullsend-ai/fullsend/issues/2269))

### Auto-merge readiness

With trustworthiness evidence accumulating, we begin reasoning about where auto-merge is safe — identifying specific codepaths or repositories where the evidence supports it and defining what the threshold looks like.
Expand Down
Loading