Account for JIRA contributor field in dashboard metrics

[aakankshaduggal]

Currently, the dashboard metrics do not appear to account for the contributor field in JIRA tickets.

Many of the larger research and exploratory tasks are collaborative in nature, and contributors are often captured using this field. Since the dashboard seems to attribute work based only on primary ownership, this may lead to incomplete or skewed representation of team contributions.

Suggested Improvement:

• Incorporate the JIRA Contributors field into the dashboard logic when calculating metrics.
• Ensure collaborative work is appropriately attributed across contributors

[accorvin]

@claude triage this

[claude]

Claude finished @accorvin's task in 2m 5s —— View job

---

Triage: Issue #281 — Account for JIRA contributor field in dashboard metrics

• Read full issue and comments
• Investigate current Jira metrics implementation
• Assess feasibility and propose approach
• Apply appropriate labels

Label applied: enhancement

---

Analysis

Current behavior: All person-level Jira metrics are fetched using assignee = "{accountId}" in JQL queries (modules/team-tracker/server/jira/person-metrics.js). Only the assignee field is considered — there is no existing handling of a contributor/collaborator field anywhere in the codebase.

This means collaborative work captured via Jira's contributor field is invisible in the dashboard.

Affected JQL queries (all in person-metrics.js):

• Resolved issues query (line 438): assignee = "${accountId}" AND resolved >= -${lookbackDays}d ...
• Incremental refresh query (line 377): assignee = "${accountId}" AND resolved >= "${sinceDateStr}" ...
• In-progress query (line 367): assignee = "${accountId}" AND status in (...) ...
• Verification query (line 280): key in (...) AND assignee = "${accountId}" ...

Fetched fields (line 17): summary, issuetype, status, assignee, resolutiondate, created, components, customfield_10028 — no contributor field included.

---

Proposed Implementation

Prerequisites:

• Need to identify the exact Jira custom field ID for the "contributor" field on your Jira instance (e.g., customfield_XXXXX). This varies per Jira installation.

Changes required:

1. person-metrics.js — JQL & field changes:

   • Add the contributor custom field to FIELDS constant
   • Modify JQL queries to use OR logic: (assignee = "{id}" OR cf[XXXXX] = "{id}") to capture issues where the person is either the assignee or a contributor
   • Bump FIELDS_VERSION to 'v2' to force re-fetch of cached data
   • Update mapIssue() to extract and store contributor information
   • Track whether the person was the assignee vs. a contributor on each issue (for metric attribution decisions)

2. Metric attribution decisions (need team input):

   • Should a contributed issue count the same as an assigned issue toward resolved count?
   • Should story points be split between assignee and contributors, or counted fully for each?
   • Should cycle time calculations include contributed issues?
   • Should the UI distinguish between "assigned" and "contributed" work?

3. Sprint report (sprint-report.js):

   • buildAssigneeBreakdown() currently groups by assignee — may need a parallel contributor breakdown

4. Frontend changes:

   • Person detail views may need a "contributed to" section alongside "assigned" work
   • Team aggregation logic needs to avoid double-counting when both assignee and contributor are on the same team

5. Cache invalidation:

   • Bumping FIELDS_VERSION will trigger a full re-fetch for all people on next refresh

---

Complexity Assessment

Moderate-to-high complexity. The JQL changes are straightforward, but the metric attribution decisions (how to count/weight contributor work vs. assigned work) have significant product implications and need team alignment before implementation.

Open Questions

1. What is the exact Jira custom field ID for the "contributor" field on your instance?
2. How should contributed work be weighted in metrics — full credit, partial credit, or tracked separately?
3. Should contributed issues appear in the same resolved/in-progress counts, or as a separate metric?

---

To move forward, please answer the open questions above and tag me with approval to implement. I'll then create a PR with the changes.