🛠️ Smarter Contributor Attribution for Planning Issues

We’ve improved how completed planning issues are credited to developers so that your planning metrics reflect who actually did the work.

Previously, each issue was attributed to its last assignee—whoever happened to hold the issue when it was closed. Because issues are often reassigned as they move through stages (development, review, QA, close), the last assignee isn’t always the person who did the work. Now we identify a primary contributor for each issue using the full assignment history and supporting signals, including:

• Who held the issue while it was in progress (and for how long)
• Who authored a linked pull request
• Who moved the issue through its key stages

This applies across both Jira and Azure DevOps, which both track assignment changes over time.

What you’ll notice:

• Completed-issue credit now lands with the developer who did the work, not just the final assignee.
• Issues that previously had no attributed developer are now correctly credited.
• No issue loses its attribution—this change only adds or redistributes credit.