Knuckles-Team Atlassian Assigned Issues Manager Workflow
CONCEPT:KG-2.12
Automatically retrieves issues assigned to the current user, flags tickets older than 7 days, and maps current coding progress to suggest new ticket backlogs.
Steps
Step 0: Atlassian Assigned-Issue Query [skill: atlassian-agent]
Agent: intake-agent
Tools: graph_query, nc_files
Query Jira for all active tickets assigned to the current user using JQL assignee = currentUser() AND statusCategory != Done and stale tickets using assignee = currentUser() AND updated <= -7d via atlassian_jira_issue tool.
Expected: assigned_issues, stale_issues
Step 1: User Interaction
Agent: processor-agent
Tools: graph_analyze, document_tools
Display the active and stale issues dashboard. Prompt the user for notes on recent progress or task updates.
Expected: progress_inputs, selected_stale_resolutions
Step 2: Atlassian Issue-Update Drafting [skill: atlassian-agent]
Agent: validator-agent
Tools: graph_query
Create suggested comment updates on Jira issues using atlassian_jira_comment tool, or generate recommended drafts for new backlog tickets to align with current work.
Expected: update_results, draft_tickets
Step 3: KG Persistence [depends_on: Step 2]
Agent: validator-agent
Tools: graph_write
Persist workflow results as nodes and edges in the Knowledge Graph. Create appropriate typed nodes with metadata and link to existing domain entities.
Output
- Atlassian Assigned Issues Manager results persisted in KG
- Structured report (MD/PDF)
- Audit trail with timestamps and agent attributions
Human Oversight Required
✅ Critical decisions require human review and approval.
Execution
Run this workflow as a dependency-ordered DAG. Steps with no unmet depends_on run in parallel; dependents run after their prerequisites complete.
- Run first (in parallel): Step 0 — Atlassian Assigned-Issue Query; Step 1 — User Interaction; Step 2 — Atlassian Issue-Update Drafting
- After level 0: Step 3 — KG Persistence
Execution: If graph-os is reachable, offload the whole DAG via graph_orchestrate action=execute_workflow (or the kg-delegate skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet depends_on in parallel, then their dependents.