Copilot's GitHub Project Edits: A Hidden Pitfall for Engineering Teams and OKRs

In the fast-paced world of software development, tools like GitHub Copilot promise to boost productivity by streamlining routine tasks. However, a recent discussion on the GitHub Community forum highlights a significant "rough edge" where Copilot's helpfulness inadvertently disrupts project management workflows, specifically within GitHub Projects.

Copilot's Edits: A Hidden Pitfall for GitHub Projects and Custom Fields

The issue, raised by user MakePixelsWork, details a frustrating scenario: instructing Copilot to update an existing issue within a repository leads to that issue being removed from the GitHub Project backlog. Even more critically, all associated custom field values—such as status, priority, and iteration—are completely wiped out. This can severely impact an engineering team's ability to track progress, manage sprints, and ultimately, monitor their OKRs for engineering teams.

Understanding the Root Cause: Projects v2 API Interaction

MakePixelsWork's inquiry to Copilot itself revealed the likely culprit. Copilot explained that its issue tool uses a draft system. When a draft is confirmed, it appears to interact with GitHub Projects v2 in a way that causes the project item to be replaced rather than simply updated. This replacement severs and then re-establishes the link between the issue and the project, leading to the loss of all custom field data. Copilot candidly described this as a "known rough edge" when editing issues via tools that use the Projects v2 API, as GitHub treats project item field values as separate from the issue itself.

> What's probably causing it
>
> The Copilot issue tool uses a draft system before saving. When a draft is confirmed, it appears to interact with GitHub Projects v2 in a way that can cause the project item to be replaced rather than updated — meaning the link between the issue and the project gets re-established fresh, losing all the custom field values (status, priority, iteration, etc.) that you had set.
>
> This is a known rough edge when editing issues through tools that use the Projects v2 API — GitHub treats the project item's field values as separate from the issue itself, so anything that disturbs the item connection can wipe those values.

Impact on Agile Workflows and OKRs for Engineering Teams

For teams relying on GitHub Projects for their agile methodologies, the loss of custom field data is more than just an inconvenience. It means losing critical context for tasks, potentially derailing sprint planning, daily stand-ups, and retrospective meetings. Imagine trying to conduct an agile retrospective template meeting when key status updates or priority changes are missing because Copilot wiped the data. More broadly, if an engineering team uses these custom fields to track progress towards specific OKRs for engineering teams, this bug directly undermines their ability to measure and report on those objectives accurately.

Proposed Workarounds and the "Lying" Copilot

The original poster suggested a workaround: instead of updating the actual issue, Copilot could simply add a comment. Interestingly, Copilot initially claimed it couldn't do this, only to retract that statement when pressed, admitting an Agent could comment. This highlights a potential area for improvement in Copilot's capabilities and transparency. The core request, however, remains that the issue should not be returned to a Draft status and should retain its association with GitHub Projects and all its data during Copilot edits.

GitHub's Response and What's Next

GitHub's automated response acknowledged the feedback, assuring the user that their input would be reviewed by product teams. While no immediate solution or workaround was provided by GitHub staff, the discussion serves as a valuable insight for developers and product managers alike. It underscores the importance of understanding how AI-powered tools interact with existing platforms, especially concerning critical project management data.

As developer productivity experts, we emphasize the need for robust integrations that maintain data integrity. While Copilot offers immense potential, awareness of such interactions is crucial for maintaining accurate project tracking and ensuring that your team's efforts towards achieving OKRs for engineering teams are not inadvertently hampered by automated tools.