Inspiration

Supervising multi-team Software Engineering capstone courses at university presents three recurring challenges:

  1. Git commit counts lie: Students who author system architecture specifications in Confluence, triage Jira backlogs, or conduct thorough Pull Request reviews look "inactive" if instructors inspect only commit graphs.
  2. Free-riding and crunches surface too late: Disengagement and single-student carries often stay hidden until Week 14 final grading.
  3. Opaque AI grading is unfair: Students distrust black-box automated scores; lecturers need structured cross-product evidence and editable coaching drafts rather than automated numerical grades.

What it does

Team Project Evidence & Rubric Assistant unifies Jira, Confluence, and the Atlassian Teamwork Graph into a transparent academic supervision cockpit (jira:projectPage + confluence:globalPage):

  • Cross-Product Teamwork Graph Aggregation (src/twgClient.js): Queries atlassianTeamMembers, atlassianUserAssignedJiraWorkItems, atlassianUserPullRequests, jiraWorkItemComments, and confluencePageContributors using Relay connections (edges { node { ... } }) so architecture and peer-review work (e.g., 11 Confluence edits + 9 PR reviews) gets full visibility.
  • Early-Warning Pedagogical Detector: Flags INACTIVE_MEMBER, SINGLE_STUDENT_CARRY, and LAST_MINUTE_BURST anomalies mid-sprint alongside a weekly scheduledTrigger snapshot stored in Forge KVS.
  • 3 Non-Negotiable Academic Guardrails:
    1. Student Self-Inspection View: Every student inspects the exact same cross-product evidence and weekly cadence seen by the lecturer.
    2. Zero Autonomous Grading: Never assigns numerical scores automatically.
    3. Lecturer-in-the-Loop Approval: AI rubric coaching (@forge/llm claude-sonnet-5) is strictly an editable draft requiring explicit Approve & Publish to Milestone Record confirmation.
  • Rovo Teaching Assistant (rovo:agent + rovo:skill): Answers cross-team supervision questions grounded in Teamwork Graph evidence via course-evidence-rubric.
  • Runs on Atlassian Eligible: Zero external network egress keeps student records inside Atlassian Cloud.

Challenges we ran into & Accomplishments

  • Built unified Jira Project Page + Confluence Global Page UI Kit views, clean wrapped badges, deterministic fallback (seeded-capstone-course) for sparse demo sites, and 3/3 passing node --test checks verified live on Atlassian Cloud.

Built With

Share this project:

Updates

Submission history