Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save wallace/8c9babeb84530b703ccc7fd2f3f58291 to your computer and use it in GitHub Desktop.

Select an option

Save wallace/8c9babeb84530b703ccc7fd2f3f58291 to your computer and use it in GitHub Desktop.
updated-with-justification
number title age_bucket age_days days_since_update comments labels assignees author suggested_bucket agent_recommendation justification confidence created_at updated_at url
99 Not possible to restore organization memberships via the API 1: >5yr 3437 736 18 enhancement, backlog, keep izuzak Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'enhancement,' indicating it is valid and worth keeping for future consideration. While it has been open for a long time (over 5 years), there has been recent activity within the last two years, including comments from multiple team members discussing its relevance and potential prioritization. The issue is not actively being worked on but remains relevant based on customer feedback and internal discussions. Therefore, it should remain in the backlog for potential future work. medium 2016-11-16 2024-04-08 https://github.com/github/enterprise-primitives/issues/99
302 (9) Quick jump to an area/function in Stafftools 1: >5yr 2488 736 5 Feature Request, backlog, keep, priority-4, stafftools aricwalker petros Close → Feature Request Keep — Backlog The issue is labeled as 'Feature Request' and 'backlog,' indicating it is valid and worth keeping for potential future work. While it is over 5 years old and has been marked stale previously, there is evidence of continued interest and relevance, as seen in recent comments from users and assignees expressing the need for this feature. Additionally, it has been assigned a priority level and added to the backlog, suggesting it is still under consideration despite the lack of active work. medium 2019-06-23 2024-04-08 https://github.com/github/enterprise-primitives/issues/302
39 Org, Enterprise account, and Repo email invitations can be accepted by anyone 2: 3-5yr 1785 736 21 enhancement, support-escalation, support-sev3, backlog, keep, priority-3 erikaxu Keep — Backlog Keep — Backlog The issue is labeled with 'backlog' and 'keep,' indicating it is considered valid and worth retaining for future work. Despite its age (1785 days) and the lack of recent updates (736 days), there is ongoing relevance as evidenced by recent comments referencing related work and customer concerns. Additionally, the issue addresses a security concern for enterprise customers, which aligns with its 'support-escalation' and 'priority-3' labels. While not actively being worked on, it remains a valid candidate for future prioritization. medium 2021-05-26 2024-04-08 https://github.com/github/enterprise-primitives/issues/39
16 Initiative: Enterprise Innersource 🚧 2: 3-5yr 1735 736 0 Initiative, keep, roadmap erikaxu phantomdata Keep — Active Close — Stale The issue is over 4 years old, has had no meaningful activity in over 2 years, and lacks recent updates or engagement. Despite being labeled as 'roadmap' and 'initiative,' there is no evidence of active work or progress. Additionally, the estimated ship dates have long passed, and no comments or updates suggest ongoing relevance. medium 2021-07-14 2024-04-08 https://github.com/github/enterprise-primitives/issues/16
15 Initiative: Token Lifecycle Management 🚧 2: 3-5yr 1735 736 2 backlog, design needed, Initiative, roadmap phantomdata Close — Stale Needs Discussion The issue is labeled 'design needed' and involves a significant initiative requiring further planning and decision-making. Although it has been reopened and updated recently, the comments indicate that there are unresolved questions about the implementation approach. The presence of multiple contributors and references to external documents suggests that further discussion is necessary to clarify the direction before active work can proceed. high 2021-07-14 2024-04-08 https://github.com/github/enterprise-primitives/issues/15
29 Bulk `Edit` users and/or groups at the enterprise/org level 2: 3-5yr 1707 736 5 enhancement, backlog, keep, product decision erikaxu Keep — Backlog Needs Discussion The issue has a 'product decision' label, indicating that further discussion or clarification is required to determine the next steps. While it is marked as 'backlog' and has been reopened, the recent comments suggest ongoing engagement and unresolved questions about the behavior of VS+GH bundles and enterprise user management. This indicates that the issue is still relevant but requires additional input or decisions before progressing. medium 2021-08-12 2024-04-08 https://github.com/github/enterprise-primitives/issues/29
40 Two organization removal events for single user with no invitation/addition in between 2: 3-5yr 1645 392 16 bug, support-escalation, support-sev2, backlog, keep, priority-4 wi11ialvl Keep — Backlog Keep — Backlog The issue is labeled as 'backlog,' indicating it is not actively being worked on but is still considered valid and worth keeping. Despite its age (1645 days) and the lack of updates in the past year, the presence of labels such as 'bug,' 'support-escalation,' and 'priority-4' suggests it remains relevant to the team and may be addressed in the future. Additionally, the detailed comments and linked resources show ongoing interest and potential for resolution. medium 2021-10-13 2025-03-19 https://github.com/github/enterprise-primitives/issues/40
17 Initiative: Policy Framework & Compliance Dashboard - 🚧 Draft 2: 3-5yr 1596 680 0 backlog, design needed, Initiative, keep, product decision, product opportunity, roadmap erikaxu erikaxu Keep — Active Needs Discussion The issue is labeled with 'design needed' and 'product decision,' indicating that further discussion and clarification are required before any actionable steps can be taken. Despite its age (1596 days) and lack of recent activity (680 days since last update), the issue remains open and contains exploratory ideas for a significant initiative. The absence of comments and incomplete tasks further suggest that this issue needs more input and refinement before progressing. medium 2021-12-01 2024-06-04 https://github.com/github/enterprise-primitives/issues/17
349 Initiative: Extend IP Allow List Policies to "User-Owned" Accounts & Repos in EMU 2: 3-5yr 1581 12 64 on track, Initiative, ip-allow-list wallace, erikaxu, robert-crandall, tchavas erikaxu Keep — Active Keep — Active The issue is labeled 'on track' and has recent updates, including progress summaries and active work by multiple assignees. It is tied to specific release milestones, with a GA target date of April 20, 2026, and ongoing development activities such as bug fixes and post-GA fanout work. The high level of engagement, including 64 comments and recent updates within the last 12 days, indicates that this initiative is actively being worked on and remains relevant. low 2021-12-15 2026-04-02 https://github.com/github/enterprise-primitives/issues/349
4722 Add capability to restore a team to the way it was prior to deletion 2: 3-5yr 1498 49 38 Feature Request, enhancement, support-escalation, support-sev3, backlog, priority-4 stacycarter Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and 'enhancement,' indicating it is a request for new functionality rather than a bug or active development task. Despite the presence of 'support-escalation' and related comments, the issue has been in the backlog for 1498 days with no recent updates or active work. The feature request should be closed and tracked through the feature request process to streamline prioritization and avoid clutter in the repository. low 2022-03-08 2026-02-25 https://github.com/github/enterprise-primitives/issues/4722
348 [Product] All GHEC customers have an enterprise account 2: 3-5yr 1490 35 70 keep erikaxu erikaxu Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent weekly updates detailing progress on Phase 3, including milestones, batch upgrades, and next steps. The assignee is actively engaged, and the issue has frequent comments and updates, indicating ongoing work and relevance. The 'keep' label further supports its active status. medium 2022-03-17 2026-03-11 https://github.com/github/enterprise-primitives/issues/348
21 Initiative: Show Outside Collaborators in Enterprise Members list DRAFT 🚧 2: 3-5yr 1420 680 0 backlog, design needed, Initiative, roadmap robert-crandall Close — Stale Needs Discussion The issue has the 'design needed' label, indicating that further discussion or clarification is required to determine the approach for implementation. Despite its age and lack of recent activity, the issue remains open and has a 'backlog' label, suggesting it is still considered valid. However, the absence of comments or active engagement highlights the need for renewed discussion to move forward. high 2022-05-25 2024-06-04 https://github.com/github/enterprise-primitives/issues/21
71 🚧 [DRAFT] Initiative: Orgs Refactor Part 2 - Creation, Transfers, Deletion, & Recovery 2: 3-5yr 1395 680 1 backlog, design needed, Initiative, roadmap erikaxu Close — Stale Keep — Backlog The issue is labeled as 'backlog' and 'design needed,' indicating it is valid and intended for future work but not actively being worked on. Despite its age (1395 days) and the lack of recent updates (680 days since last activity), the detailed description and references suggest it is still relevant and part of a larger initiative. It should remain in the backlog for potential prioritization later. medium 2022-06-20 2024-06-04 https://github.com/github/enterprise-primitives/issues/71
155 Connected Enterprise Initiatives Snapshot 2: 3-5yr 1358 736 4 backlog, inactive, keep, product opportunity erikaxu, jackieytan iamclement Keep — Backlog Close — Stale The issue has been inactive for over two years, with the last update occurring 736 days ago. While it references several initiatives, many of them are either completed or have been deprioritized, as indicated by comments from assignees. Additionally, the Connected Enterprise team responsible for this work has been dissolved, and related functionality has been transferred to the licensing team. This suggests the issue is no longer relevant in its current form and should be closed as stale. medium 2022-07-27 2024-04-08 https://github.com/github/enterprise-primitives/issues/155
476 Task: Refactor the `app/views/businesses/_member_filter.html.erb` to make it more readable 2: 3-5yr 1356 1254 0 enhancement, keep, task tchavas Keep — Backlog Close — Stale The issue has been open for over 3 years with no meaningful activity in the past 1254 days. It lacks recent engagement, comments, or assignee activity, and the task described appears to be outdated or deprioritized. The 'enhancement' label does not indicate active work, and the absence of updates suggests it is no longer relevant. medium 2022-07-28 2022-11-07 https://github.com/github/enterprise-primitives/issues/476
4726 Request: Provide Team Maintainers the ability to delete Parent Teams 2: 3-5yr 1349 49 8 Feature Request, enhancement, support-escalation, support-sev3, keep, product opportunity wdpankow Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and 'enhancement,' indicating it is a request for new functionality rather than a bug or active development task. While it has been reopened and has some recent activity, the comments suggest it is being tracked as a product opportunity rather than actively worked on. Additionally, the 'keep' label suggests it should remain in the backlog for feature tracking, but the appropriate bucket for feature requests is 'Close → Feature Request' to ensure it is handled through the feature request process. medium 2022-08-05 2026-02-25 https://github.com/github/enterprise-primitives/issues/4726
4888 EMU's should have finer access controls (such as Team Maintainer) w/IDP Group Sync 2: 3-5yr 1343 30 19 on track, identity-tnt reeseglasscock Keep — Active Needs Discussion The issue has an 'on track' label and recent comments discussing documentation updates and potential feature requests. However, there is ambiguity about whether the issue should be closed after documentation updates or if it should continue to track a feature request. Additionally, there is no clear resolution or next steps outlined in the comments, and further clarification from Engineering or Product Management is needed. This signals that the issue requires additional discussion before a definitive triage decision can be made. low 2022-08-11 2026-03-16 https://github.com/github/enterprise-primitives/issues/4888
4754 GHEC Team Sync re-invites users after their external identity and org removal (race condition) 2: 3-5yr 1339 26 21 support-escalation, support-sev3, keep patrikpolyak Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev3,' indicating it is a priority for customer support. Despite its age (1339 days), it was reopened recently and has had updates within the last 26 days, showing ongoing engagement. Additionally, the issue has 21 comments, including recent reports from customers, suggesting it remains relevant and requires active attention. medium 2022-08-15 2026-03-20 https://github.com/github/enterprise-primitives/issues/4754
178 🚧 Product Ideation: Multi-enterprise support 🚧 2: 3-5yr 1329 707 9 backlog, inactive, Initiative, product opportunity, roadmap erikaxu Close — Stale Keep — Backlog The issue is labeled as 'backlog,' indicating it is valid and worth keeping but not actively being worked on. Despite its age (1329 days) and the lack of updates in the past 707 days, the comments show consistent engagement from multiple stakeholders, including references to customer feedback and strategic enterprise needs. This suggests the issue remains relevant and could be prioritized in the future roadmap. medium 2022-08-25 2024-05-07 https://github.com/github/enterprise-primitives/issues/178
253 Expose internal repository count for organizations 2: 3-5yr 1307 736 3 enhancement, support-escalation, support-sev3, backlog, keep gm3dmo Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'enhancement,' indicating it is valid and worth keeping for future consideration. Although it has been open for a long time (1307 days) and has not been updated recently (736 days), the comments suggest it has been acknowledged and added to a broader initiative for tracking purposes. There is no indication that the issue is stale or resolved, and it aligns with customer needs and product impact, making it suitable for the backlog. medium 2022-09-16 2024-04-08 https://github.com/github/enterprise-primitives/issues/253
262 💡 🚧 Allow ownerless EAs to enable Org Owner Self-Promotion 2: 3-5yr 1304 736 4 backlog, keep erikaxu Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'keep,' indicating it is valid and worth keeping but not actively being worked on. Although the issue is old (1304 days) and has not been updated recently (736 days since last update), the problem described remains relevant, as it impacts a significant number of enterprise accounts and poses a risk to customer retention and revenue. The comments show some engagement and discussion about potential solutions, but no clear resolution or active work is evident. Therefore, it should remain in the backlog for potential future prioritization. medium 2022-09-19 2024-04-08 https://github.com/github/enterprise-primitives/issues/262
313 GHEC (non EMUs) - request to make the SAML message for pending org invites in SAML enforced orgs mor 2: 3-5yr 1299 293 6 good first issue, support-escalation, support-sev2, backlog, keep, priority-4 stacycarter Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'good first issue,' indicating it is valid but not actively being worked on. While the issue has been reopened recently and has some recent activity (last updated 293 days ago), the comments suggest it is a low-priority enhancement with limited customer impact. It is still relevant and worth keeping for potential future work, but it does not require immediate attention. medium 2022-09-23 2025-06-25 https://github.com/github/enterprise-primitives/issues/313
4887 Support "Type" filter for Org members, as it only works for Admins 2: 3-5yr 1281 30 3 identity-tnt hpsin Keep — Active Keep — Backlog The issue is still open and has had recent activity within the last 30 days, indicating some level of ongoing interest or relevance. While it has been marked as stale previously, the author has recently re-engaged with the discussion, suggesting it is still valid and worth keeping in the backlog for potential future work. The lack of assignees and active work signals that it is not currently being prioritized, but it remains a valid issue. low 2022-10-11 2026-03-16 https://github.com/github/enterprise-primitives/issues/4887
413 [Feature Request]: Rate limits for inviting Orgs to join Enterprise plans 2: 3-5yr 1278 595 0 Feature Request, backlog, keep mrjf Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed solution to address potential abuse of Enterprise plan invitations. It has been reopened but has had no meaningful activity for 595 days, indicating it is not actively being worked on. The 'backlog' label suggests it is valid but should be tracked through the feature request process rather than remaining open as an issue. medium 2022-10-15 2024-08-28 https://github.com/github/enterprise-primitives/issues/413
420 Initiative: Refine EA Trial experience to support manually-created EMU/Invoice trials 2: 3-5yr 1276 736 1 Initiative, roadmap erikaxu Close — Stale Keep — Backlog The issue is still open and labeled as 'Initiative' and 'roadmap,' indicating it is part of a broader plan but not actively prioritized. While it has not been updated in over two years, the description and comments suggest it is still valid and impactful, particularly for improving the trial experience and reducing manual effort for Sales Support teams. The estimated ship date is marked as 'TBD: Not Prioritized at this time,' further supporting its placement in the backlog. high 2022-10-17 2024-04-08 https://github.com/github/enterprise-primitives/issues/420
471 Review TODO in AccountScreeningProfile 2: 3-5yr 1258 736 1 backlog, on track, inactive, keep mutle mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog,' indicating it is valid and worth keeping but not actively being worked on. Although it has been inactive for a significant period (736 days since the last update), the recent comment from jackieytan suggests there is still interest in revisiting the TODO. The issue remains open and relevant, but it is not currently on track or actively being addressed. medium 2022-11-04 2024-04-08 https://github.com/github/enterprise-primitives/issues/471
542 Sunset Enterprise Organization Trials 2: 3-5yr 1227 208 0 backlog, inactive, Initiative, roadmap erikaxu Close — Stale Close — Stale The issue is over 3 years old, labeled as 'inactive,' and has not been updated in over 200 days. Additionally, there are no comments or recent activity, and the estimated ship date has long passed, suggesting the issue is outdated and no longer relevant. low 2022-12-05 2025-09-19 https://github.com/github/enterprise-primitives/issues/542
4886 [Feature Request]: Default Team assignment at Org level 2: 3-5yr 1225 30 5 identity-tnt potaders Keep — Active Close → Feature Request The issue is labeled as a feature request ('identity-tnt') and describes a proposed solution for default team assignments at the organization level. While there has been some engagement, the issue has been open for over 3 years and marked as stale by automation. There is no indication of active work or prioritization, and feature requests are typically tracked through a separate process. Closing it as a feature request is appropriate to streamline tracking. low 2022-12-07 2026-03-16 https://github.com/github/enterprise-primitives/issues/4886
567 Support Enterprise-specific Onboarding Programs 2: 3-5yr 1220 652 0 Initiative, roadmap erikaxu Close — Stale Close — Stale The issue is over 3 years old and has not been updated in over 650 days. It has no comments or active engagement, and the lack of recent activity suggests it is no longer relevant or being actively pursued. Additionally, the roadmap and initiative labels do not indicate current prioritization or progress. high 2022-12-12 2024-07-01 https://github.com/github/enterprise-primitives/issues/567
580 Org-level rate limiting 2: 3-5yr 1218 595 5 backlog, inactive, keep, incident-repair, incident-repair-ignore mutle mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and remains open, indicating it is still considered valid but not actively being worked on. While it has breached SLA and has been flagged for prioritization, recent comments suggest that the issue was scoped for investigation rather than immediate implementation. The lack of recent updates (595 days) and the presence of 'inactive' and 'incident-repair-ignore' labels further support that this issue is not currently active but still relevant for future consideration. medium 2022-12-14 2024-08-28 https://github.com/github/enterprise-primitives/issues/580
610 [Bounty] Unauthorized access and become owner of the enterprise account using mutation `acceptEnterp 2: 3-5yr 1197 4 19 backlog, bounty, keep, SECURITY sentinel Keep — Active Keep — Backlog The issue is labeled as 'backlog' and 'security,' indicating it is valid and important but not actively being worked on. Recent comments show ongoing discussion and analysis, but no immediate resolution or active work. The issue remains relevant and should be kept for future prioritization. medium 2023-01-04 2026-04-10 https://github.com/github/enterprise-primitives/issues/610
657 Stafftools Improvement for Org Transfers & Upgrades 2: 3-5yr 1175 274 6 epic, keep erikaxu Keep — Active Keep — Backlog The issue is valid and contains detailed information about proposed improvements to Stafftools for organization transfers and upgrades. While it has been reopened and has recent comments, there is no indication that active work is currently being done on it. The presence of the 'epic' and 'keep' labels suggests it is still considered important but not actively prioritized, making it suitable for the backlog. medium 2023-01-26 2025-07-15 https://github.com/github/enterprise-primitives/issues/657
742 [Feature Request]: Allow the use of GitHub Apps to manage IP Allowlists 2: 3-5yr 1143 252 2 Feature Request, backlog, on track, inactive, keep bxtp4p Keep — Backlog Keep — Backlog The issue is labeled as 'Feature Request' and 'backlog,' indicating it is valid and worth keeping but not actively being worked on. Despite its age (1143 days) and lack of recent updates (last updated 252 days ago), the comments show continued interest from multiple customers (e.g., Universal Music, Intel), suggesting it remains relevant. The 'on track' label may indicate future prioritization, but no active work or assignee is currently associated with the issue. medium 2023-02-27 2025-08-06 https://github.com/github/enterprise-primitives/issues/742
754 Batch: Investigate all locations where a user can upgrade to an enterprise-plan org, and instead red 2: 3-5yr 1140 425 8 batch, on track, keep AnthonyLaye AnthonyLaye Keep — Backlog Keep — Active The issue is labeled 'on track' and 'keep,' indicating active work or relevance. Although the issue is over three years old, it was reopened and has recent comments (425 days ago) discussing specific tasks and updates. Additionally, the assignee, AnthonyLaye, has been actively engaging with the issue, providing updates and clarifications. These signals suggest the issue is still being worked on and is relevant to ongoing efforts. medium 2023-03-02 2025-02-13 https://github.com/github/enterprise-primitives/issues/754
776 Initiative: EMU-Owned Repo Access & Auditing 2: 3-5yr 1132 187 18 blocked, on track, Initiative, roadmap pndemo erikaxu Needs Discussion Keep — Active The issue is labeled 'on track' and 'roadmap,' indicating active work and prioritization. Recent comments from the assignee and other contributors show ongoing engagement, with updates on timelines and progress. Several tasks have been completed, and there are clear next steps outlined in the 'Enhance!' section. The issue is still open and relevant, with active development and communication around its goals. low 2023-03-10 2025-10-10 https://github.com/github/enterprise-primitives/issues/776
786 Implement Stafftools report with export option 2: 3-5yr 1127 571 0 blocked, inactive, keep robert-crandall Keep — Backlog Close — Stale The issue has been inactive for 571 days, has no recent comments or updates, and is labeled as 'inactive'. Additionally, the 'blocked' label suggests that progress is unlikely without further action, and the age of the issue (over 3 years) indicates it may no longer be relevant. medium 2023-03-15 2024-09-20 https://github.com/github/enterprise-primitives/issues/786
4729 Sev2: [EMU] Linked IdP Group Issues with Parent ↔ Child Teams 2: 3-5yr 1115 49 23 support-escalation, support-sev2 jusuchin85 Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case that requires active attention. Additionally, there has been recent activity within the last 49 days, including multiple comments and related discussions in Slack and Zendesk tickets. The issue is still open and pertains to a critical customer-impacting problem, making it relevant and actively in-progress. low 2023-03-27 2026-02-25 https://github.com/github/enterprise-primitives/issues/4729
902 Initiative: Address EMU feature gaps & friction points 3: 1-3yr 1092 208 0 design needed, on track, inactive, Initiative, roadmap, ghe-meters lildude, gpadak, pndemo, erikaxu, robert-crandall, jackieytan erikaxu Close — Stale Needs Discussion The issue is labeled 'design needed' and 'on track,' indicating that it requires further discussion and planning to determine the next steps. Despite its age (1092 days) and lack of recent updates (208 days), the issue remains open and has multiple assignees, suggesting it is still considered relevant. Additionally, the issue outlines a broad initiative with multiple tasks and dependencies, which further supports the need for discussion to clarify priorities and scope before proceeding. low 2023-04-19 2025-09-19 https://github.com/github/enterprise-primitives/issues/902
960 Customers (enterprise owners) need self-serve solution to free up enterprise name that they used in 3: 1-3yr 1077 736 4 Feature Request, support-escalation, support-sev3, inactive, keep stacycarter Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and describes a request for a new functionality to enable auto-cleanup or self-service deletion of expired/cancelled enterprise trials. While there has been some discussion, the issue has been inactive for 736 days, and related work appears to be tracked in other issues such as https://github.com/github/mEAO/issues/1333. This indicates that the feature request is not actively being worked on in this issue and should be closed and tracked through the feature request process. medium 2023-05-03 2024-04-08 https://github.com/github/enterprise-primitives/issues/960
981 Searching for `outside collaborators` using email address isn't working at organization level 3: 1-3yr 1072 736 1 enhancement, support-escalation, support-sev2, backlog, inactive, keep deepumrtn Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'enhancement,' indicating that it is valid and worth keeping but not actively being worked on. Despite being open for over 1000 days and having limited recent activity (last update was 736 days ago), the issue remains relevant as it addresses a specific functionality gap impacting customers, as evidenced by the linked Zendesk ticket and the detailed description of the problem. The 'inactive' label suggests it is not currently prioritized, but the 'keep' label confirms it should remain in the backlog for potential future work. medium 2023-05-09 2024-04-08 https://github.com/github/enterprise-primitives/issues/981
1020 Initiative: Self-Serve GHE Metered Phase 3 (Post-Public GA) 3: 1-3yr 1063 490 0 backlog, on track, Initiative, roadmap, ghe-meters jackieytan Close — Stale Keep — Backlog The issue is labeled as 'backlog' and 'on track,' indicating it is valid and part of a planned roadmap but not actively being worked on. Despite its age (1063 days) and lack of recent updates (490 days), it references ongoing initiatives and related tasks, suggesting it remains relevant for future work. No recent activity or assignee indicates it is not currently active but should be retained for potential prioritization later. high 2023-05-18 2024-12-11 https://github.com/github/enterprise-primitives/issues/1020
1035 GraphQL domain verification not available to GitHub Apps 3: 1-3yr 1056 450 23 support-escalation, support-sev3, on track, inactive, keep gm3dmo Keep — Backlog Keep — Active The issue is labeled 'on track' and has recent engagement, including a comment from an assignee indicating that a PR with a proposed fix is open and will be picked up by the team in the near future. Additionally, the issue is marked as a 'support escalation' with a severity level of 'sev3,' indicating it is being actively monitored and worked on. Despite its age and the time since the last update, the presence of recent comments and an open PR demonstrate that the issue is still relevant and actively being addressed. medium 2023-05-25 2025-01-20 https://github.com/github/enterprise-primitives/issues/1035
1114 [Initiative]: Request to "join an organization" 3: 1-3yr 1038 736 3 Feature Request, backlog, Initiative, roadmap maya-ross Close — Stale Close → Feature Request The issue is labeled as 'Feature Request' and has not had meaningful activity in over two years. Additionally, a comment from alexlato22 indicates that this idea is already being considered within the 'Request a Feature' framework, suggesting it is being tracked elsewhere. Closing this issue as a feature request is appropriate to streamline tracking and planning. high 2023-06-12 2024-04-08 https://github.com/github/enterprise-primitives/issues/1114
1135 Batch: Rate limiting for API and scheduling background jobs 3: 1-3yr 1030 736 0 backlog, batch, on track, inactive, keep mutle mutle Keep — Backlog Close — Stale The issue has been inactive for 736 days despite being reopened, with no recent updates or comments. It has a 'inactive' label and no evidence of ongoing work or engagement, suggesting it is outdated and no longer relevant. medium 2023-06-20 2024-04-08 https://github.com/github/enterprise-primitives/issues/1135
1214 [Feature Request]: Investigate/Transfer organization Zuora balance when being added to an Enterprise 3: 1-3yr 1014 736 1 Feature Request, on track, inactive, keep AnthonyLaye AnthonyLaye Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and proposes a new functionality to address the transfer of Zuora balances when organizations are added to Enterprise Accounts. Despite being reopened, the issue has been inactive for 736 days with minimal engagement (only one comment). There is no evidence of active work or recent prioritization, and the 'on track' label appears outdated given the lack of updates. Closing this issue as a feature request ensures it can be tracked through the appropriate process for future consideration. medium 2023-07-05 2024-04-08 https://github.com/github/enterprise-primitives/issues/1214
4755 GHEC (non-EMU) Team Sync - Customer UI/UX and docs issues 3: 1-3yr 994 46 12 support-escalation, support-sev2, on track stacycarter Keep — Active Keep — Active The issue is labeled 'on track,' indicating active work is being done. It has recent engagement, with comments from multiple stakeholders discussing next steps and potential solutions. Although the issue is aged at 994 days, the last update was 46 days ago, showing ongoing activity. The severity level (support-sev2) further emphasizes its importance and urgency, making it clear that this issue is actively being addressed. low 2023-07-25 2026-02-28 https://github.com/github/enterprise-primitives/issues/4755
1359 Refactor batch selection in Enterprise and Org admin views 3: 1-3yr 965 485 1 backlog, keep, tech debt mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'tech debt,' indicating it is valid and worth keeping but not actively being worked on. Although it is aged at 965 days and has not been updated in 485 days, the issue remains relevant as it references unifying user experience and closing related bugs and requests. The recent comment provides additional context and customer feedback, reinforcing its importance for future prioritization. medium 2023-08-24 2024-12-16 https://github.com/github/enterprise-primitives/issues/1359
1430 Epic: Implement metered GHEC upsell functionality 3: 1-3yr 938 91 26 backlog, design needed, epic, on track, inactive, keep, roadmap, ghe-meters, copilot-enterprise mutle, jdennes, erikaxu erikaxu Keep — Active Needs Discussion The issue is labeled with 'design needed' and recent comments indicate ongoing discussions about key decisions and design iterations. While the issue is old (938 days), it has been reopened and updated recently (91 days ago), with active engagement from multiple contributors. The complexity and scope of the issue, along with unresolved questions raised in the comments, suggest that further discussion is required before moving forward. medium 2023-09-20 2026-01-14 https://github.com/github/enterprise-primitives/issues/1430
1473 Batch: CfB/Basic EA People's Pages (Admin & Non-Admin) 3: 1-3yr 926 707 0 backlog, batch, inactive, keep, copilot-enterprise mutle, erikaxu jackieytan Keep — Backlog Close — Stale The issue has been inactive for 707 days, with no comments or meaningful updates since its reopening. It is labeled as 'inactive' and 'backlog,' indicating it is not currently being worked on. Additionally, the lack of recent engagement suggests it is no longer relevant or prioritized. medium 2023-10-02 2024-05-08 https://github.com/github/enterprise-primitives/issues/1473
1488 [Feature Request]: IP allowlist fine-grained permission 3: 1-3yr 924 63 1 Feature Request, backlog, ip-allow-list, keep hpsin Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and 'backlog,' indicating it is a request for new functionality rather than an active bug or task. The body explicitly states that this is a low-priority item opened for posterity and tracking, and there has been minimal recent activity (last update 63 days ago, only one comment). Closing it as a feature request aligns with the process for tracking such requests separately. medium 2023-10-04 2026-02-11 https://github.com/github/enterprise-primitives/issues/1488
1486 [Feature Request]: Org permission for "Invite user to org" and other distinct privileges 3: 1-3yr 924 736 0 Feature Request, backlog, keep hpsin Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and has been in the backlog for over 2 years with no recent updates or activity. It outlines a proposed solution and alternatives but does not indicate active work or engagement. Closing it as a feature request ensures it can be tracked through the appropriate process for prioritization and development. medium 2023-10-03 2024-04-08 https://github.com/github/enterprise-primitives/issues/1486
1497 For metered conversion, Azure Select Subscription page should have Activation page as background 3: 1-3yr 922 484 3 backlog, keep, ghe-meters robert-crandall Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and remains open, indicating it is still considered valid and worth addressing in the future. While there has been no recent activity in the past 484 days, the comments suggest that the problem persists and has not been resolved. Additionally, the issue is tied to the 'Metered GHE and GHAS Post-GA' initiative, which implies it is part of a broader effort and may be revisited later. medium 2023-10-06 2024-12-17 https://github.com/github/enterprise-primitives/issues/1497
1502 Improvement: add model-layer validation preventing users from having both EA owner and EA billing ma 3: 1-3yr 919 736 0 backlog, keep tchavas Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and describes a valid improvement that is worth keeping for future consideration. Although it has been open for a long time (919 days) and has not been updated recently (736 days since last update), the described problem remains relevant and unresolved. There is no indication that the issue is stale or outdated, and it has not been marked as done or resolved. The lack of urgency mentioned in the body further supports its placement in the backlog. medium 2023-10-09 2024-04-08 https://github.com/github/enterprise-primitives/issues/1502
1521 Epic: Review EMU & SCIM member management behaviors 3: 1-3yr 911 243 4 epic, keep jackieytan Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'keep,' indicating it is a significant and valid item to retain. Although it has been open for a long time (911 days) and hasn't been updated in 243 days, recent comments suggest ongoing interest and relevance. Additionally, the issue is pending PM review for scheduling, which confirms it is still considered for future work. Therefore, it should remain in the backlog for potential prioritization. medium 2023-10-16 2025-08-15 https://github.com/github/enterprise-primitives/issues/1521
1566 [Feature Request]: Stafftools - remove org SAML config when enforced at enterprise level 3: 1-3yr 897 571 0 Feature Request, backlog, done, keep gennaropalma Close — Done Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed enhancement to Stafftools functionality. Despite being reopened, it has been inactive for 571 days with no recent comments or updates, and there is no indication of active work or prioritization. Closing it as a feature request aligns with the process for tracking such requests separately. high 2023-10-31 2024-09-20 https://github.com/github/enterprise-primitives/issues/1566
1579 [Epic] Epic: Expand self-serve Slug rename coverage 3: 1-3yr 889 571 0 backlog, done, epic, keep erikaxu Close — Done Keep — Backlog The issue is labeled as 'backlog,' indicating it is valid and intended for future work. Despite its age (889 days) and lack of recent updates (571 days since last activity), the detailed description and tasks suggest it is still relevant and worth keeping for potential prioritization later. There are no signals of active work or recent engagement, but the 'epic' label implies it is part of a larger initiative that may be revisited. high 2023-11-08 2024-09-20 https://github.com/github/enterprise-primitives/issues/1579
1599 Batch: Remove pop-up dialog when upgrading Free/Team org to new EA 3: 1-3yr 880 553 1 batch, done, inactive, keep AnthonyLaye Close — Done Close — Stale The issue is over 880 days old, with no meaningful activity in the past 553 days. It has an 'inactive' label and the work appears to have been marked as 'done' previously. Additionally, there is no evidence of active engagement or progress, suggesting it is outdated and no longer relevant. high 2023-11-16 2024-10-09 https://github.com/github/enterprise-primitives/issues/1599
1682 Follow up work required for deprecated `OrganizationInvitation.inviter` GraphQL field 3: 1-3yr 827 462 1 backlog, on track, keep jdennes jdennes Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'on track,' indicating it is valid and worth keeping but not actively being worked on. Although the issue is over two years old and has not been updated in over a year, it references ongoing work related to deprecated GraphQL fields and includes actionable follow-up tasks. The presence of an assignee and recent comments discussing the removal timeline further support its relevance for future prioritization. medium 2024-01-09 2025-01-08 https://github.com/github/enterprise-primitives/issues/1682
2050 [MVP] Expired enterprise trial to GitHub Team 3: 1-3yr 817 532 15 backlog, epic, keep raymondtiu Keep — Active Keep — Backlog The issue has the 'backlog' label, indicating it is valid and worth keeping but not actively being worked on. Although it has been reopened and has significant age (817 days), the last update was 532 days ago, suggesting it is not currently a priority. The comments indicate some past engagement, but there is no recent activity or evidence of active progress. Therefore, it should remain in the backlog for potential future prioritization. medium 2024-01-19 2024-10-30 https://github.com/github/enterprise-primitives/issues/2050
1723 [Epic]: Enterprises should be able to enforce their IP allowlists without orgs overriding it 3: 1-3yr 811 635 2 Feature Request, backlog, done, epic, ip-allow-list, keep hpsin Close — Done Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed solution to enhance enterprise-level IP allowlist functionality. Despite being reopened, it has been inactive for 635 days, and there is no evidence of active work or recent engagement from assignees. The presence of the 'backlog' label suggests it is not currently prioritized, and the 'done' label appears to be incorrectly applied as the issue is still open. Closing this as a feature request aligns with the process for tracking such proposals. high 2024-01-25 2024-07-19 https://github.com/github/enterprise-primitives/issues/1723
1785 Manual user reinstatement inconsistent in parent/child teams in an EMU 3: 1-3yr 795 616 3 emu bug, support-escalation, support-sev2, inactive, keep adamrr724 Keep — Backlog Keep — Backlog The issue is labeled as 'emu bug' and 'support-escalation,' indicating it is valid and important. However, it also has the 'inactive' label and has not been updated in over 600 days, suggesting it is not actively being worked on. Recent comments confirm that further investigation is needed, but there is no urgency indicated, and the issue is on the FR board for future work. Therefore, it should remain in the backlog for potential prioritization later. medium 2024-02-09 2024-08-07 https://github.com/github/enterprise-primitives/issues/1785
1853 Consider optimising `RemoveOrgMemberRepositoryStarsJob` and `RemoveOrgMemberWatchedRepositoriesJob` 3: 1-3yr 769 635 0 backlog, keep mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'keep,' indicating it is still considered valid and worth retaining for future work. Although it has been inactive for 635 days, it references related issues and data sources, suggesting it is still relevant. There is no indication that the issue is resolved or outdated, so it should remain in the backlog for potential future prioritization. medium 2024-03-07 2024-07-19 https://github.com/github/enterprise-primitives/issues/1853
1852 Provide a way to clean up customers who ended up with a large number of suspended users (due to SCIM 3: 1-3yr 769 484 2 support-escalation, backlog, keep mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'support-escalation,' indicating it is valid and worth keeping but not actively being worked on. Despite its age (769 days) and lack of recent updates (484 days), the issue references multiple related tickets and has ongoing relevance due to SCIM provisioning concerns. It has not been marked as stale or resolved, and there is no indication that it should be closed at this time. medium 2024-03-07 2024-12-16 https://github.com/github/enterprise-primitives/issues/1852
1893 Initiative: Customers can understand numbers reflected in Enterprise's People Page Filters & UX 3: 1-3yr 761 141 9 backlog, design needed, Initiative erikaxu Needs Discussion Needs Discussion The issue has the 'design needed' label, indicating that further discussion or clarification is required to determine the next steps. Additionally, the issue is part of an initiative and has multiple references, tasks, and comments discussing various aspects of the problem, suggesting that it is complex and requires alignment before proceeding. While it is labeled as 'backlog,' the presence of recent comments and unresolved design considerations makes 'Needs Discussion' the most appropriate bucket. low 2024-03-15 2025-11-25 https://github.com/github/enterprise-primitives/issues/1893
1909 [Internal Feedback] [feature request] Ability to switch settings context from enterprise back to org 3: 1-3yr 755 582 1 Feature Request, backlog, done, design needed, keep, product decision, internal feedback kfrank therzka Close — Done Needs Discussion The issue has conflicting signals, including labels such as 'Feature Request,' 'design needed,' and 'product decision,' indicating that further discussion or clarification is required to determine the next steps. While it has been reopened, the last update was 582 days ago, and the comment from the assignee suggests it is tied to another issue but lacks clarity on its current priority or resolution path. high 2024-03-21 2024-09-10 https://github.com/github/enterprise-primitives/issues/1909
1946 Rename `User#business_id` field to avoid confusions 3: 1-3yr 740 505 3 backlog, done, keep, tech debt mutle Close — Done Keep — Backlog The issue is labeled as 'backlog' and addresses a valid concern about the `business_id` field causing confusion. While it has not been actively worked on recently (last update was 505 days ago), the comments indicate ongoing relevance, with teams still encountering issues related to this field. The 'done' label appears to be misapplied, as the work described has not been completed. Therefore, it should remain in the backlog for future prioritization when changes to the `users` table are feasible. high 2024-04-05 2024-11-26 https://github.com/github/enterprise-primitives/issues/1946
2096 [Initiative] Org-ownership Role Assignment 3: 1-3yr 736 673 9 backlog, Initiative divyagandhi01 Close — Stale Keep — Backlog The issue is labeled as 'backlog' and remains open, indicating it is valid and worth keeping for future work. While it has not been updated in over 673 days, the detailed problem statement, action plan, and comments suggest it is still relevant and tied to ongoing initiatives. There is no indication that the issue is resolved or stale, and it aligns with broader organizational goals and dependencies. medium 2024-04-09 2024-06-11 https://github.com/github/enterprise-primitives/issues/2096
4738 [Bug] Missing organization team sync app installation for enterprise level configured team sync 3: 1-3yr 736 27 19 bug, support-escalation, on track, sev2 blkdm0n dvo-dev Keep — Active Keep — Active The issue is labeled 'on track,' indicating active work is being done to address it. It has recent engagement with comments from multiple contributors within the last month, and an assignee is actively involved. Additionally, the issue is marked as 'sev2' and 'support-escalation,' suggesting it is a high-priority bug affecting customers. These signals confirm that the issue is still relevant and actively being worked on. low 2024-04-08 2026-03-19 https://github.com/github/enterprise-primitives/issues/4738
4885 [Epic] Enterprise Teams can be assigned more org roles 3: 1-3yr 728 30 0 epic, inactive, identity-tnt divyagandhi01 Close — Stale Close — Stale The issue is over 2 years old, labeled as 'inactive,' and has not been updated in the last 30 days. Additionally, there are no comments or recent activity to suggest it is still relevant or being worked on. It appears to be outdated and should be closed as stale. low 2024-04-17 2026-03-16 https://github.com/github/enterprise-primitives/issues/4885
2436 Add Cancel/Downgrade option to self-serve EA billing pages 3: 1-3yr 726 29 36 Feature Request, design needed, on track, product decision anna-talley Keep — Active Needs Discussion The issue has multiple labels indicating the need for further clarification and decision-making, such as 'design needed' and 'product decision.' Additionally, the comments show ongoing discussions about the complexity of the downgrade process and whether a PM should be involved to revisit the issue. Despite its age, the issue has recent activity (29 days ago) and continues to generate engagement, suggesting it is still relevant but requires further discussion to determine the next steps. low 2024-04-18 2026-03-17 https://github.com/github/enterprise-primitives/issues/2436
1998 Refactor org members table to be a11y compliant 3: 1-3yr 721 572 1 backlog, done, keep baturn Close — Done Keep — Backlog The issue is labeled as 'backlog,' indicating it is valid and worth keeping but not actively being worked on. Although it has been reopened and has had minimal activity in the past 572 days, the issue remains relevant as it pertains to accessibility compliance and aligns with GitHub's UI standards. The recent comment suggests it is still being considered within lower-priority accessibility work, supporting its placement in the backlog for future prioritization. high 2024-04-23 2024-09-20 https://github.com/github/enterprise-primitives/issues/1998
4898 Investigate why team failing to sync sometimes report retry with cache locked error instead of faile 3: 1-3yr 714 30 3 sev2, incident-repair, incident-repair-ignore, identity-tnt guperrot Keep — Active Keep — Backlog The issue is labeled with 'incident-repair' and 'sev2,' indicating it is a repair item related to an availability incident and has medium severity. Although it has been open for 714 days and has not been actively updated recently, the issue remains valid and relevant as it pertains to improving logging and investigating cache locking errors during team sync failures. The comments suggest that it is still being tracked and requires further action, but it is not actively being worked on at the moment. Therefore, it should remain in the backlog for future prioritization. low 2024-04-30 2026-03-16 https://github.com/github/enterprise-primitives/issues/4898
2209 Spike: Move organizations to their own table 3: 1-3yr 674 243 3 keep lildude Keep — Backlog Keep — Backlog The issue is valid and addresses a significant technical concern regarding the organization and user table structure in the database. While there has been some recent discussion (243 days ago) and collaboration interest from other teams, there is no indication of active work or urgency. The 'keep' label and the issue's description explicitly state that this is something to be worked on as time allows, suggesting it belongs in the backlog for future prioritization. medium 2024-06-10 2025-08-15 https://github.com/github/enterprise-primitives/issues/2209
2225 Request to add "Explore more" tile about enabling enterprise audit log features 3: 1-3yr 672 464 4 Feature Request, support-escalation, support-sev3, backlog, done, keep, product decision stacycarter Close — Done Needs Discussion The issue has multiple labels indicating it requires further input, such as 'product decision' and 'design needed.' Additionally, recent comments suggest uncertainty about how to proceed, with contributors debating whether to include the feature in the backlog or remove it from the feature request board. The issue also involves considerations about design and prioritization, which necessitate further discussion before a clear path forward can be determined. high 2024-06-12 2025-01-06 https://github.com/github/enterprise-primitives/issues/2225
2235 Bug: Enterprise Admins can't recover deleted personal namespace repos/can't see deleted forks. 3: 1-3yr 669 540 2 Feature Request, keep y-me-y Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and describes enhancements to existing functionality rather than a bug fix. It has been added to an enhancement tracking issue (#776) and discussed as a potential improvement for GA readiness. Despite being reopened, there has been no meaningful activity for over 540 days, and the comments suggest it is being tracked elsewhere. Closing it as a feature request aligns with the process for managing such issues. medium 2024-06-15 2024-10-22 https://github.com/github/enterprise-primitives/issues/2235
2303 Batch: Migrate company owned standalone GHEC orgs to Enterprise accounts 3: 1-3yr 651 125 10 batch, done, keep AnthonyLaye AnthonyLaye Close — Done Keep — Active The issue is actively being worked on, as evidenced by recent comments and engagement from multiple contributors, including the assignee AnthonyLaye. The 'done' label appears to be incorrectly applied, as the issue remains open and unresolved. Additionally, the initiative and epic links suggest ongoing relevance, and the feature flag mentioned in the comments indicates that the work is still in progress. Therefore, this issue should remain active for continued tracking and resolution. high 2024-07-02 2025-12-11 https://github.com/github/enterprise-primitives/issues/2303
2337 🚧 Initiative: Implement Additional Friction for Self-serve Destructive Actions 3: 1-3yr 644 303 0 Initiative, product decision erikaxu Needs Discussion Needs Discussion The issue is labeled with 'product decision,' indicating that further discussion or clarification is required to determine the next steps. Additionally, there has been no recent activity for 303 days, and the tasks outlined in the issue are still vague and incomplete. The lack of comments or assignee engagement further supports the need for discussion before progressing. low 2024-07-10 2025-06-16 https://github.com/github/enterprise-primitives/issues/2337
2346 [Feature Request] Admin unable to see who is requesting (RAF) Copilot 3: 1-3yr 643 457 12 Feature Request, bug, design needed, keep, product decision SirHawbly Close → Feature Request Needs Discussion The issue has multiple signals indicating it requires further discussion before a decision can be made. It is labeled as 'Feature Request,' 'design needed,' and 'product decision,' suggesting that input from design and product teams is necessary to determine the next steps. Additionally, the comments highlight ongoing scoping efforts and related customer feedback, but no clear resolution or active work is evident. The age of the issue and the lack of recent updates further reinforce the need for clarification and prioritization. medium 2024-07-10 2025-01-13 https://github.com/github/enterprise-primitives/issues/2346
4884 [Tracking] Enterprise Teams v2 3: 1-3yr 622 2 79 on track, Initiative, Enterprise Roles, erp-tracking, identity-tnt mtodd dawita66 Keep — Active Keep — Active The issue is labeled 'on track,' indicating active work and progress. It has recent updates (2 days ago) and a high level of engagement with 79 comments. Additionally, it is assigned to a specific individual (mtodd), and the detailed milestones and objectives suggest it is still relevant and actively being worked on. These signals strongly support keeping the issue in the 'Keep — Active' bucket. low 2024-07-31 2026-04-13 https://github.com/github/enterprise-primitives/issues/4884
2434 Failed Invitations is expensive to combine org and repo invitations 3: 1-3yr 617 288 10 backlog, design needed, keep, product decision gwwar Keep — Backlog Needs Discussion The issue has the 'design needed' and 'product decision' labels, indicating that further discussion and clarification are required before proceeding. While the issue is valid and has recent engagement (comments within the last year), it is not actively being worked on, and there are unresolved questions about the design and implementation. The presence of linked design work and related discussions suggests that the issue is still in the planning phase and needs more input before moving forward. medium 2024-08-06 2025-07-01 https://github.com/github/enterprise-primitives/issues/2434
2456 Review database indexes for `organization_invitations` 3: 1-3yr 616 328 0 backlog, keep, tech debt, not planned mutle Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'tech debt,' indicating it is valid and worth keeping for future consideration. Although it has been inactive for 328 days, the problem described remains relevant and unresolved. There are no signals suggesting it should be closed, and it is not actively being worked on, making 'Keep — Backlog' the appropriate bucket. medium 2024-08-07 2025-05-22 https://github.com/github/enterprise-primitives/issues/2456
2467 Epic: Update $0 conversion behavior for metered accounts to prevent confusion & abuse 3: 1-3yr 614 296 1 epic, keep, ghe-meters erikaxu Keep — Active Needs Discussion The issue is labeled as 'epic' and involves multiple related tasks (#2503, #2543, #2544, #2435), indicating it is part of a broader initiative. However, it has been reopened and lacks recent activity (296 days since last update). The comments suggest ongoing concerns about the root cause and potential solutions, but no clear resolution or active work is evident. The complexity and need for evaluation of options suggest further discussion is required to determine the next steps. medium 2024-08-09 2025-06-23 https://github.com/github/enterprise-primitives/issues/2467
2466 [Epic] Update Org to EA Direct Upgrade flows to create Metered EAs instead of Volume 3: 1-3yr 614 208 3 epic, inactive, keep, ghe-meters raymondtiu, erikaxu erikaxu Keep — Active Keep — Backlog The issue is valid and pertains to updating flows for metered enterprise accounts, which aligns with the publicly launched metered GHE and GHAS. Although the issue has been inactive for 208 days, it is labeled 'epic' and 'keep,' indicating it is still relevant and worth retaining for future work. Additionally, recent comments suggest some ongoing interest and potential next steps, but there is no evidence of active work or immediate priority, making it suitable for the backlog. medium 2024-08-09 2025-09-19 https://github.com/github/enterprise-primitives/issues/2466
2490 Bug: Sometimes trials fail to convert if Zuora callback is delayed 3: 1-3yr 609 27 3 bug, keep gwwar Keep — Active Keep — Backlog The issue is labeled as 'bug' and 'keep,' indicating it is valid and worth retaining. While it has been open for over 600 days, there was recent activity 27 days ago, including comments discussing potential solutions and related cases. The issue remains relevant, but there is no evidence of active work or immediate prioritization, making it suitable for the backlog. medium 2024-08-14 2026-03-19 https://github.com/github/enterprise-primitives/issues/2490
2501 Modify organization programmatic access grants to use ProgrammaticAccessGrant.bulk_revoke 3: 1-3yr 608 510 0 keep robert-crandall Keep — Backlog Close — Stale The issue has been open for 608 days with no meaningful activity in the last 510 days. It has no comments or assignee engagement, and the 'keep' label does not indicate active work or prioritization. Given its age and lack of updates, it is likely outdated or no longer relevant. medium 2024-08-15 2024-11-21 https://github.com/github/enterprise-primitives/issues/2501
2524 Epic: Separate `/people/failed_invitations` page between failed org invites and failed repo invites 3: 1-3yr 604 303 0 backlog, epic, keep raymondtiu Keep — Active Keep — Backlog The issue is labeled as 'backlog' and 'epic,' indicating it is valid and worth keeping but not actively being worked on. Despite its age (604 days) and lack of recent updates (303 days since last activity), the detailed description and tasks suggest it is still relevant and actionable. There are no comments or assignees, further supporting its status as a backlog item rather than an active issue. medium 2024-08-19 2025-06-16 https://github.com/github/enterprise-primitives/issues/2524
2531 Investigate if IP Allow List Errors are incorrectly display for certain errors 3: 1-3yr 603 41 2 keep robert-crandall gwwar Keep — Active Close — Stale The issue has been open for over 600 days with limited recent activity (last update was 41 days ago). Recent comments suggest that the impact of the issue has diminished significantly, with fewer support requests related to it. Additionally, improvements such as better internal documentation and changes to Enterprise IP allowlist behavior may have mitigated the problem. These signals indicate that the issue is no longer actively relevant and can be closed as stale. medium 2024-08-20 2026-03-04 https://github.com/github/enterprise-primitives/issues/2531
2526 [Exclusion tracking] Invoiced enterprise orgs are excluded from the automated upgrade to enterprise 3: 1-3yr 603 504 0 keep raymondtiu Keep — Backlog Close — Stale The issue has been open for 603 days with no meaningful activity in the past 504 days. It lacks recent engagement, comments, or updates, and the described work appears to be outdated or deprioritized. The 'keep' label does not align with the prolonged inactivity, suggesting the issue is no longer relevant or actionable. medium 2024-08-19 2024-11-27 https://github.com/github/enterprise-primitives/issues/2526
2542 [Customer Feedback]: Consider an account-level setting to disable Copilot license requests 3: 1-3yr 600 99 2 Feature Request, keep, Member Feature Requests erikaxu kathleenqin Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a potential enhancement to provide an account-level setting for disabling Copilot license requests. While it has some recent activity (last updated 99 days ago), there is no indication of active work or prioritization. Feature requests are typically tracked through a separate process, making this issue suitable for closure under the 'Close → Feature Request' bucket. medium 2024-08-22 2026-01-06 https://github.com/github/enterprise-primitives/issues/2542
2972 (Enhancement) Ability to Remove Orgs from EMU Accounts 3: 1-3yr 596 391 19 Feature Request, backlog, keep, product decision, not planned amquesada Close → Feature Request Needs Discussion The issue has multiple labels indicating it requires further clarification and decision-making, such as 'product decision' and 'Feature Request.' Despite being open for 596 days, it has had recent engagement within the last year, including detailed comments exploring potential solutions and impacts. The complexity of the issue, including its implications for compliance and operational efficiency, suggests that further discussion is needed to determine the best course of action. medium 2024-08-27 2025-03-20 https://github.com/github/enterprise-primitives/issues/2972
2568 Improvement: Further performance improvements and cleanup for business.remove_users_from_business 3: 1-3yr 595 399 0 backlog, keep AnthonyLaye Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'keep,' indicating it is valid and worth retaining for future consideration. Although it has been open for 595 days and has not been updated in 399 days, the detailed body suggests that the improvements and cleanup tasks are still relevant and could be picked up later. There is no indication that the issue is stale or resolved, and it explicitly mentions that it should remain in the backlog for future prioritization. medium 2024-08-28 2025-03-12 https://github.com/github/enterprise-primitives/issues/2568
2578 [Exclusion tracking] Accounts in top OSS programs experience issues in seats count or lose products 3: 1-3yr 593 398 3 keep raymondtiu Keep — Backlog Keep — Backlog The issue is valid and addresses a critical migration concern for top OSS programs, but it has not seen meaningful activity in over a year. The payment banner issue mentioned in the comments has been resolved, but the broader migration plan and investigation into seat counts and product access remain incomplete. The 'keep' label indicates that the issue is still worth retaining for future work, but it is not actively being worked on at the moment. medium 2024-08-29 2025-03-13 https://github.com/github/enterprise-primitives/issues/2578
2604 Fully ship metered trials by default 3: 1-3yr 588 489 0 good first issue, keep robert-crandall Keep — Backlog Close — Stale The issue has been open for 588 days with no meaningful activity in the last 489 days. It has no comments or assignees, and the referenced feature flag appears to have been fully shipped, making the issue likely outdated or irrelevant. medium 2024-09-04 2024-12-12 https://github.com/github/enterprise-primitives/issues/2604
2603 Spike: Clean up restorables on purging soft deleted organization 3: 1-3yr 588 489 0 keep pndemo Keep — Backlog Close — Stale The issue has been open for 588 days with no meaningful activity in the last 489 days. It has no comments or assignees, and while it references related initiatives, there is no indication of active work or recent engagement. The 'keep' label does not align with the prolonged inactivity, suggesting the issue is outdated and no longer relevant. medium 2024-09-04 2024-12-12 https://github.com/github/enterprise-primitives/issues/2603
4894 Enterprise team other background jobs need to limit write block scopes and throttle writes 3: 1-3yr 587 30 0 identity-tnt guperrot Keep — Active Keep — Backlog The issue is still open and contains detailed acceptance criteria, indicating it is valid and worth keeping. However, there has been no recent activity (last update was 30 days ago), and no assignees are currently working on it. The 'identity-tnt' label suggests it is related to a specific domain but not actively prioritized. Therefore, it should remain in the backlog for potential future work. low 2024-09-04 2026-03-16 https://github.com/github/enterprise-primitives/issues/4894
4895 Enterprise team mapping background jobs need to limit write block scopes and throttle writes 3: 1-3yr 587 30 0 identity-tnt guperrot Keep — Active Keep — Backlog The issue is open and contains detailed technical requirements and acceptance criteria, indicating it is still valid and relevant. However, there has been no recent activity (last update was 30 days ago), and no assignees are currently working on it. The 'identity-tnt' label suggests it is part of a broader initiative but not actively prioritized at the moment. Therefore, it should be kept in the backlog for future consideration. low 2024-09-04 2026-03-16 https://github.com/github/enterprise-primitives/issues/4895
4896 Enterprise team reconcile/runner jobs need to limit write block scopes and throttle writes 3: 1-3yr 587 30 0 identity-tnt guperrot Keep — Active Keep — Backlog The issue is valid and contains detailed technical information about necessary improvements to background jobs, including limiting write block scopes and implementing write throttling. However, it has been open for 587 days with no recent activity in the last 30 days, and there are no assignees or comments indicating active work. The 'identity-tnt' label suggests it is relevant to the team's scope but not currently prioritized. Therefore, it should remain in the backlog for potential future work. low 2024-09-04 2026-03-16 https://github.com/github/enterprise-primitives/issues/4896
4897 [Batch] Enterprise team jobs need to limit write block scopes and throttle writes 3: 1-3yr 587 30 0 batch, inactive, identity-tnt guperrot Close — Stale Close — Stale The issue is over 587 days old, labeled as 'inactive,' and has had no meaningful activity or comments in the last 30 days. Additionally, the body indicates that the work has been deprioritized and the feature has been disabled, making the tasks unnecessary at the moment. These signals suggest the issue is outdated and no longer relevant. low 2024-09-04 2026-03-16 https://github.com/github/enterprise-primitives/issues/4897
2636 [Feature Request]: Enable Customers to reclaim a slug from one of their current deleted accounts th 3: 1-3yr 586 485 0 Feature Request, backlog, keep, product decision erikaxu Close → Feature Request Close → Feature Request The issue is labeled as 'Feature Request' and 'backlog,' indicating it is a request for new functionality rather than a bug or active work item. It has been open for 586 days with no meaningful activity in the last 485 days, and there are no comments or assignees. The lack of recent engagement and the nature of the issue suggest it should be closed and tracked through the feature request process instead. medium 2024-09-06 2024-12-16 https://github.com/github/enterprise-primitives/issues/2636
4893 [Bug] Enabling ESM while still disabling ESM in the background can lead to missing org mappings 3: 1-3yr 586 30 0 bug, identity-tnt guperrot Keep — Active Keep — Backlog The issue is labeled as 'bug' and 'identity-tnt', indicating it is a valid problem related to enterprise team synchronization. Although it is 586 days old, it was updated 30 days ago, suggesting some recent attention. However, there are no comments or assignees, and it is not actively being worked on. Therefore, it should be kept in the backlog for future prioritization. low 2024-09-05 2026-03-16 https://github.com/github/enterprise-primitives/issues/4893
4892 Allow team-sync setup without admin consent 3: 1-3yr 573 30 0 identity-tnt owlstronaut Keep — Active Keep — Backlog The issue is valid and addresses a customer pain point regarding admin consent for team-sync setup. It has a detailed description of the problem and potential solutions, but there has been no recent activity or assignee engagement in the last 30 days. The 'identity-tnt' label suggests it is related to identity management, which is still relevant. However, given its age (573 days) and lack of active work, it is best categorized as backlog for future prioritization. low 2024-09-19 2026-03-16 https://github.com/github/enterprise-primitives/issues/4892
2697 Improve EMU deletion speed during purging 3: 1-3yr 572 474 1 keep lildude Keep — Backlog Keep — Backlog The issue is valid and describes a performance problem with EMU deletion during purging, along with potential solutions. Although it has been reopened and has not seen recent activity (last update was 474 days ago), the 'keep' label indicates it is still considered relevant and worth retaining for future work. There is no indication that the issue has been resolved or is no longer applicable, so it should remain in the backlog for potential prioritization later. medium 2024-09-20 2024-12-27 https://github.com/github/enterprise-primitives/issues/2697
2751 Review and restructure serviceownership of enterprise settings 3: 1-3yr 558 328 0 backlog, keep, not planned pndemo Keep — Backlog Keep — Backlog The issue is labeled as 'backlog' and 'keep,' indicating it is valid and worth retaining for future consideration. Despite its age (558 days) and lack of recent activity (328 days since last update), the issue describes a structural improvement to enterprise settings that could address ownership and SLO concerns. There are no comments or active assignees, but the problem remains relevant and unresolved, making it suitable for the backlog. medium 2024-10-04 2025-05-22 https://github.com/github/enterprise-primitives/issues/2751
4891 Remove `enterprise_teams_migrate_from_cfb` feature flag 3: 1-3yr 551 30 1 identity-tnt stves Keep — Active Needs Discussion The issue involves a potentially complex cleanup of a feature flag with considerations for race conditions and unaffiliated accounts. While the issue is valid, the recent comment from AnthonyLaye questioning whether the flag should still be cleaned up indicates that further clarification or discussion is needed before proceeding. The labels and activity level do not suggest active work, but the technical nuances require input from relevant stakeholders. low 2024-10-11 2026-03-16 https://github.com/github/enterprise-primitives/issues/4891
2787 Payment method stays as "card"even when customer chooses "Azure" 3: 1-3yr 546 232 4 bug, keep, not planned, ghe-meters sosundaram Keep — Backlog Needs Discussion The issue has been reopened and contains recent comments discussing the underlying logic and potential confusion around the 'billing_type' behavior. While the issue is old, the comments suggest ongoing uncertainty about whether the current behavior is correct or actionable. Labels like 'keep' and 'not planned' indicate it is not actively being worked on but still requires further clarification or decision-making to determine next steps. medium 2024-10-15 2025-08-25 https://github.com/github/enterprise-primitives/issues/2787
2807 Epic: Implement a max retention date for failed invitations 3: 1-3yr 538 440 0 epic, keep raymondtiu Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'keep,' indicating it is a significant initiative worth retaining. While it has been open for 538 days and has not been updated in 440 days, the detailed description, tasks, and references suggest it is still a valid and relevant issue. There is no indication that the work has been completed or that the issue is stale, but it is not actively being worked on at the moment. Therefore, it should remain in the backlog for potential future prioritization. medium 2024-10-23 2025-01-30 https://github.com/github/enterprise-primitives/issues/2807
2814 Epic: Optimize side effects or member to org add/remove actions 3: 1-3yr 537 301 3 epic, on track, keep mutle mutle Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and prioritization. Although the last update was 301 days ago, recent comments from the assignee and collaborators show ongoing engagement, including references to production data and prioritization updates. Additionally, several tasks within the issue have been completed, and the assignee is actively involved, suggesting the issue is still relevant and in progress. medium 2024-10-25 2025-06-18 https://github.com/github/enterprise-primitives/issues/2814
2898 Batch: Require SToS enterprise accounts to sign the new GitHub GCA 3: 1-3yr 511 57 0 batch, done AnthonyLaye Close — Done Keep — Backlog The issue is valid and contains actionable tasks that are partially completed, as indicated by the checklist in the body. However, there has been no recent activity in the past 57 days, and the 'done' label likely refers to subtasks rather than the overall issue being resolved. The absence of comments and assignees suggests it is not actively being worked on but remains relevant for future progress. high 2024-11-20 2026-02-17 https://github.com/github/enterprise-primitives/issues/2898
2896 Epic: Force SToS standalone GHEC organizations to upgrade to a new enterprise account 3: 1-3yr 511 56 0 blocked, epic AnthonyLaye Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'blocked,' indicating it is part of a larger initiative but currently cannot proceed due to dependencies or challenges. While it has been open for a long time (511 days) and has not been updated recently (56 days), the tasks listed in the body suggest that work is still pending and relevant. There are no comments or recent activity, but the issue remains valid and worth keeping for future prioritization. low 2024-11-20 2026-02-18 https://github.com/github/enterprise-primitives/issues/2896
2895 Initiative: Force remaining standalone GHEC-plan organizations to upgrade to an enterprise account 3: 1-3yr 511 136 0 blocked, Initiative AnthonyLaye, raymondtiu, tchavas AnthonyLaye Needs Discussion Keep — Active The issue is labeled as 'blocked' and 'Initiative,' indicating it is part of an ongoing project. Despite its age of 511 days, it has recent updates (136 days ago) and active assignees (AnthonyLaye, raymondtiu, tchavas), suggesting continued engagement. The detailed breakdown in the body shows that work is still in progress, with dependencies and plans outlined for future actions. Therefore, it remains relevant and actively worked on. low 2024-11-20 2025-11-30 https://github.com/github/enterprise-primitives/issues/2895
2931 Missing custom footer for site admins on GHES 3: 1-3yr 504 400 5 support-escalation, support-sev3, keep patrikpolyak Keep — Backlog Keep — Backlog The issue is valid and has detailed context about a customer-impacting bug related to GHES custom footer rendering for site admins. Although it has been open for a long time (504 days) and hasn't been updated in 400 days, it is labeled 'support-escalation' and 'support-sev3,' indicating its importance. The 'keep' label further suggests it should remain in the backlog for future prioritization. There is no indication that the issue has been resolved or is stale, and it remains relevant for affected customers. medium 2024-11-27 2025-03-11 https://github.com/github/enterprise-primitives/issues/2931
2951 Task Optimize `RemoveUsersOrganizationOrchestration` step `remove_org_user_email_settings` 3: 1-3yr 497 301 2 keep gwwar Keep — Backlog Keep — Backlog The issue is valid and contains detailed technical notes and references for optimizing a specific step in the codebase. Although it has been open for 497 days and hasn't been updated in 301 days, the 'keep' label indicates that it is still considered relevant and worth retaining for future work. There is no indication of active work or recent engagement, so it is best categorized as backlog for potential future prioritization. medium 2024-12-04 2025-06-18 https://github.com/github/enterprise-primitives/issues/2951
2946 Task Optimize `RemoveUsersOrganizationOrchestration` step `save_organization_settings` 3: 1-3yr 497 301 0 keep gwwar Keep — Backlog Close — Stale The issue has been open for 497 days with no meaningful updates in the last 301 days. It has no comments or active engagement, and the 'keep' label does not indicate active work or prioritization. Given the prolonged inactivity, it is likely outdated or no longer relevant. medium 2024-12-04 2025-06-18 https://github.com/github/enterprise-primitives/issues/2946
2942 Task Optimize `AddUsersOrganizationOrchestration` step `update_integration_installation_rate_limits` 3: 1-3yr 497 301 0 keep mutle mutle Keep — Backlog Keep — Backlog The issue is labeled as 'keep,' indicating it is still considered valid and worth retaining. Although it has been open for 497 days and has not been updated in 301 days, it has been reopened, suggesting continued relevance. There are no recent comments or activity, and it is not actively being worked on, so it fits the backlog category. medium 2024-12-04 2025-06-18 https://github.com/github/enterprise-primitives/issues/2942
4883 [Epic] FGPs for team management 3: 1-3yr 490 2 97 epic, on track, roadmap, identity-tnt mutle dawita66 Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and prioritization. It has recent updates (2 days ago) and significant engagement with 97 comments, showing ongoing activity. Additionally, it is tied to a critical objective for the ERP preview goal, making it highly relevant and actively pursued. low 2024-12-11 2026-04-13 https://github.com/github/enterprise-primitives/issues/4883
3086 [Feature Request]: Staff API: Make Enterprise Self Serve 3: 1-3yr 450 352 5 Feature Request, keep NickLiffen Keep — Backlog Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed solution for automating a manual process via a staff API. Despite being reopened, there has been no meaningful activity in over 350 days, and the issue does not appear to be actively worked on. It should be closed and tracked through the feature request process instead. medium 2025-01-20 2025-04-28 https://github.com/github/enterprise-primitives/issues/3086
3136 🚧 Initiative: "On By Default" GH Connect for metered GHES customers 3: 1-3yr 441 436 0 backlog, design needed, Initiative erikaxu erikaxu Close — Stale Needs Discussion The issue has the 'design needed' label, indicating that further exploration and clarification are required before work can proceed. Additionally, while it is labeled as 'backlog,' the lack of recent activity (436 days since the last update) and absence of comments suggest that the initiative may need renewed discussion to determine its feasibility and priority. The tasks and rollout plan are incomplete, further supporting the need for discussion. high 2025-01-29 2025-02-03 https://github.com/github/enterprise-primitives/issues/3136
3160 Epic: Support direct CAP lookups to the relevant resources 3: 1-3yr 439 338 0 backlog, epic, keep raymondtiu Keep — Active Keep — Backlog The issue is labeled as 'backlog' and 'epic,' indicating it is a valid and significant piece of work that is intended to be addressed in the future. Although it has been open for 439 days and has not been updated in 338 days, the detailed description and tasks suggest it is still relevant and worth keeping for future prioritization. There is no indication that the issue is stale or resolved, and no recent activity suggests it is not actively being worked on at the moment. medium 2025-01-30 2025-05-12 https://github.com/github/enterprise-primitives/issues/3160
4882 Rotate Azure certificate auth secrets by January 2030 3: 1-3yr 429 30 0 keep, identity-tnt stves Keep — Active Keep — Backlog The issue is valid and serves as a placeholder for a future task to rotate Azure certificate auth secrets by January 2030. It has the 'keep' label and is related to identity management ('identity-tnt' label). Although it hasn't been updated recently, the task is still relevant and not time-sensitive, as the certificate expires in 2030. Therefore, it should remain in the backlog for future action. medium 2025-02-10 2026-03-16 https://github.com/github/enterprise-primitives/issues/4882
4880 Cleanup team#migration_complete 3: 1-3yr 426 30 0 identity-tnt stves Keep — Active Keep — Backlog The issue is valid and outlines clear acceptance criteria for cleanup work related to a completed migration. However, it has been open for over a year with no recent activity or assignee, indicating it is not actively being worked on. The lack of comments and updates suggests it is not urgent but still worth keeping for future prioritization. low 2025-02-13 2026-03-16 https://github.com/github/enterprise-primitives/issues/4880
4881 [Internal Feedback] Team view shows member count in place of nested team count 3: 1-3yr 426 30 0 internal feedback, identity-tnt adityasharad Keep — Active Keep — Backlog The issue is valid and pertains to incorrect member and team counts displayed in the team view, which could impact user experience. It is labeled as 'internal feedback' and 'identity-tnt,' indicating it is relevant to the team responsible for identity-related features. Although the issue is over a year old and has not been updated in 30 days, it does not have any signals suggesting it is stale or resolved. Therefore, it should remain in the backlog for potential future prioritization. low 2025-02-12 2026-03-16 https://github.com/github/enterprise-primitives/issues/4881
3214 Bug: Organization upgrade attachment failures is causing trust tier issues 3: 1-3yr 425 285 0 bug, backlog, keep AnthonyLaye Keep — Backlog Keep — Backlog The issue is labeled as 'bug' and 'backlog,' indicating it is valid and worth keeping but not actively being worked on. Despite its age (425 days) and lack of recent updates (285 days since last activity), the issue describes a clear problem with organization upgrade attachment failures affecting trust tier calculations, which remains relevant. There are no comments or assignees, further supporting its placement in the backlog for potential future prioritization. medium 2025-02-13 2025-07-03 https://github.com/github/enterprise-primitives/issues/3214
3236 Review business.async_member for accuracy and speed 3: 1-3yr 419 317 0 on track, keep mutle robert-crandall Keep — Backlog Keep — Active The issue is labeled 'on track' and 'keep,' indicating it is actively being worked on or considered. Although there has been no recent activity in 317 days, the assignee 'mutle' suggests ongoing ownership. The issue remains open and addresses a valid concern about the accuracy and efficiency of the `business.async_member` method, which is relevant to the repository's functionality. medium 2025-02-19 2025-06-02 https://github.com/github/enterprise-primitives/issues/3236
3245 Configurable::MembersCanCreateRepositories::PublicRepoCreationRestricted: Public repo creation canno 3: 1-3yr 418 302 1 keep, not planned app/sentry Keep — Backlog Keep — Backlog The issue is valid and has a detailed comment providing context about the problem and its historical background. However, it has not been actively worked on recently (302 days since last update), and the 'not planned' label indicates it is not currently prioritized. The 'keep' label suggests it is worth retaining for potential future consideration. medium 2025-02-21 2025-06-16 https://github.com/github/enterprise-primitives/issues/3245
4753 Intel (P+ customer) reports "Team sync seems to be slower or unresponsive" 3: 1-3yr 414 46 18 support-escalation, support-sev2, on track carlosjnaranjo Keep — Active Keep — Active The issue is labeled 'support-escalation', 'support-sev2', and 'on track', indicating it is actively being worked on and has a high priority due to its impact on a P+ customer. Despite its age of 414 days, there has been recent activity (46 days ago) and ongoing discussion in the comments about technical limitations and potential solutions. The customer has approved lowering the priority, but the issue remains open and relevant, requiring further action to address the underlying concerns. low 2025-02-24 2026-02-27 https://github.com/github/enterprise-primitives/issues/4753
3300 Promote unaffiliated business role to a real role 3: 1-3yr 405 29 4 keep robert-crandall Keep — Active Keep — Backlog The issue is valid and outlines a necessary improvement to the handling of the `unaffiliated` business role, which has become increasingly important with new product rollouts. Although the issue has been open for over a year, it was recently updated (29 days ago) with detailed comments and alternative solutions, indicating ongoing interest and relevance. The 'keep' label further supports retaining this issue for future prioritization, but there is no evidence of active work or assignment, making it suitable for the backlog. medium 2025-03-05 2026-03-16 https://github.com/github/enterprise-primitives/issues/3300
3337 Request: fix Business::PeopleDependency tests that are broken in EMU and MT test modes 3: 1-3yr 397 166 1 on track, inactive, keep mayamessinger Keep — Active Keep — Active The issue has the 'on track' label, indicating active work or prioritization, and recent engagement from a commenter providing detailed findings about the failures. Although the last update was 166 days ago, the issue remains open and relevant as it is blocking changes to the PeopleDependency affecting MT environments. The 'inactive' label may reflect slower progress due to the high effort required, but the issue is still being tracked and worked on. medium 2025-03-14 2025-10-31 https://github.com/github/enterprise-primitives/issues/3337
3336 ActiveRecord::RecordNotUnique: [redacted] MySQL error code 1062: Trilogy::ProtocolError (see Splunk 3: 1-3yr 397 299 1 keep app/sentry Keep — Backlog Keep — Backlog The issue is valid and contains detailed error information, including a Sentry link and a recent comment providing additional context about the error's origin. However, there has been no activity for 299 days, and no assignees are currently working on it. The 'keep' label indicates that the issue is still relevant and worth retaining for future work, but it is not actively being addressed at this time. medium 2025-03-14 2025-06-20 https://github.com/github/enterprise-primitives/issues/3336
3364 Consider moving `OrganizationInvitation#accept` work to orchestration/background job 3: 1-3yr 391 119 0 keep, tech debt jdennes Keep — Active Keep — Backlog The issue is labeled as 'tech debt' and 'keep,' indicating it is valid and worth retaining for future work. Although it has been open for over a year and has not been updated in 119 days, the problem described is still relevant and unresolved. There is no indication of active work or recent engagement, so it fits the backlog category. medium 2025-03-20 2025-12-17 https://github.com/github/enterprise-primitives/issues/3364
3363 Get `team.remove_member` audit log entries to be created when a team is deleted 3: 1-3yr 391 169 3 keep raymondtiu Keep — Active Needs Discussion The issue has been reopened and contains active discussion about its feasibility and implementation, including concerns raised by stakeholders about potential audit log spam and product limitations. The labels and comments suggest that further clarification and decision-making are required before proceeding, making 'Needs Discussion' the most appropriate bucket. medium 2025-03-19 2025-10-28 https://github.com/github/enterprise-primitives/issues/3363
3389 Request for change to help with abuse 3: 1-3yr 386 279 4 on track, keep, tracking:engineering fundamentals, scorecard:abuse wallace fundamentals-bot Keep — Backlog Keep — Active The issue is labeled 'on track' and has recent engagement from the assignee, Wallace, who has been actively working on the security exception related to the scorecard. Although the last update was 279 days ago, the presence of 'on track' and 'tracking:engineering fundamentals' labels indicates that the issue is still relevant and being monitored as part of an ongoing initiative. The comments also show progress on the exception submission and approval, suggesting active work is being done. medium 2025-03-25 2025-07-10 https://github.com/github/enterprise-primitives/issues/3389
3471 🚧 [Placeholder] Initiative: Enterprise-owned Organizations do not mandate Org Admins 4: 6mo-1yr 363 6 1 backlog, Initiative erikaxu Keep — Active Keep — Backlog The issue is labeled as 'backlog' and remains open, indicating it is valid and worth keeping for future consideration. Although it has been open for nearly a year, it was updated recently (6 days ago), and there is a relevant comment from a user providing additional context and requirements. This suggests the issue is still relevant but not actively being worked on at the moment. low 2025-04-17 2026-04-09 https://github.com/github/enterprise-primitives/issues/3471
3497 [CpL: M1.1] Nice to have: Gather information on projected license count changes 4: 6mo-1yr 355 257 0 keep, task AnthonyLaye Keep — Backlog Close — Stale The issue has been open for 355 days with no meaningful activity in the last 257 days. It lacks recent engagement, comments, or updates, and appears to be inactive despite being reopened. The absence of assignees and progress signals suggests it is no longer actively pursued or relevant. medium 2025-04-25 2025-08-01 https://github.com/github/enterprise-primitives/issues/3497
3496 [CpL: M1.1] Pre-ship: Get clarity on downgrading Copilot plans 4: 6mo-1yr 355 257 0 keep, task AnthonyLaye Keep — Backlog Close — Stale The issue has been open for 355 days with no updates in the past 257 days, indicating a lack of recent engagement or progress. Additionally, there are no comments or assignees, suggesting it is not actively being worked on. The labels and state do not indicate active prioritization, and the issue appears to be outdated. medium 2025-04-25 2025-08-01 https://github.com/github/enterprise-primitives/issues/3496
4879 [Task] Enable `read_from_replicas` for the `PATCH /organizations/:org_id/team/:team_id/team-sync/gro 4: 6mo-1yr 342 30 0 task, identity-tnt dinonuggies1 Keep — Active Keep — Backlog The issue is valid and outlines a clear task to optimize database read operations for a specific endpoint, which aligns with the platform's scalability goals. However, it has been open for 342 days with no recent updates or active engagement in the last 30 days, and no assignees are currently working on it. The 'task' label indicates it is actionable but not urgent, suggesting it should remain in the backlog for future prioritization. low 2025-05-07 2026-03-16 https://github.com/github/enterprise-primitives/issues/4879
3561 IP allow list from installed app UI issues 4: 6mo-1yr 338 1 4 design needed, keep, product decision mutle Keep — Active Needs Discussion The issue has the 'design needed' and 'product decision' labels, indicating that further discussion and clarification are required before actionable steps can be taken. Recent comments show active engagement from multiple contributors, including suggestions and design considerations, but no clear resolution or decision has been made yet. The issue is still open and was updated recently, signaling ongoing relevance and the need for further deliberation. medium 2025-05-12 2026-04-13 https://github.com/github/enterprise-primitives/issues/3561
3590 Backfill and enable use of BusinessUserAccount in GHES 4: 6mo-1yr 330 134 3 backlog, keep, tech debt mutle Keep — Active Keep — Backlog The issue is labeled as 'backlog' and 'tech debt,' indicating it is valid and worth keeping but not actively being worked on. Although there has been no update in 134 days, the comments suggest future plans to address the issue, and it remains relevant to ongoing maintenance efforts. Therefore, it should remain in the backlog for potential future prioritization. medium 2025-05-20 2025-12-02 https://github.com/github/enterprise-primitives/issues/3590
4878 Update conversion to outside collaborator UX for business team members 4: 6mo-1yr 327 30 3 identity-tnt eggyhead Keep — Active Needs Discussion The issue has a detailed description of the problem and proposed requirements, but recent comments indicate that further clarification is needed from the product team regarding the expected behavior and implementation details. The presence of the 'identity-tnt' label and engagement from multiple stakeholders, including product team members, suggests that the issue requires additional discussion before moving forward. low 2025-05-22 2026-03-16 https://github.com/github/enterprise-primitives/issues/4878
4877 [Feature request] Reflect IdP group name changes in the Org team view/APIs 4: 6mo-1yr 323 30 0 identity-tnt fmacar3na Keep — Active Close → Feature Request The issue is labeled as a feature request ('identity-tnt') and describes a desired enhancement to reflect IdP group name changes in the Org team view/APIs. There has been no recent activity (last update was 30 days ago), no assignees, and no comments indicating active work. This aligns with the criteria for closing and tracking the issue through the feature request process. low 2025-05-27 2026-03-16 https://github.com/github/enterprise-primitives/issues/4877
3604 Initiative: Additional FGPs request related to enterprise administration 🚧 4: 6mo-1yr 322 322 0 Initiative raymondtiu raymondtiu Needs Discussion Close — Stale The issue has been open for 322 days with no updates or comments since its creation. Despite being labeled as an 'Initiative,' there is no evidence of active work or engagement, and the tasks listed have not progressed. The lack of activity and updates suggests the issue is no longer relevant or actively pursued. low 2025-05-27 2025-05-27 https://github.com/github/enterprise-primitives/issues/3604
3625 Migrate DB Read Operations to Replicas for `github/team_discussions` REST API Endpoints 4: 6mo-1yr 319 131 1 keep lildude becco Keep — Active Keep — Backlog The issue is valid and addresses an important scalability concern for the `github/team_discussions` REST API endpoints. While it has been open for 319 days and has not been updated in 131 days, the presence of the 'keep' label and the detailed acceptance criteria suggest it is still relevant and worth keeping in the backlog for future prioritization. There is no indication of active work or recent engagement, so it does not belong in the 'Keep — Active' bucket. medium 2025-05-30 2025-12-05 https://github.com/github/enterprise-primitives/issues/3625
4764 Migrate DB Read Operations to Replicas for `github/enterprise_teams` REST API Endpoints 4: 6mo-1yr 319 43 1 fanout tracking becco Keep — Active Keep — Backlog The issue is valid and addresses an important scalability concern for the `github/enterprise_teams` REST API endpoints. It has a clear set of acceptance criteria and resources provided for implementation. However, it has not been actively worked on recently (43 days since last update), and there are no assignees or indications of immediate progress. The 'fanout tracking' label suggests it is part of a broader initiative but not currently prioritized. Therefore, it should remain in the backlog for future consideration. low 2025-05-30 2026-03-02 https://github.com/github/enterprise-primitives/issues/4764
3624 Migrate DB Read Operations to Replicas for `github/org_invites` REST API Endpoints 4: 6mo-1yr 319 217 0 keep becco Keep — Backlog Keep — Backlog The issue is valid and addresses an important scalability concern for the `github/org_invites` REST API endpoints. However, it has been inactive for 217 days, with no recent updates or engagement. The 'keep' label indicates it is worth retaining, but the lack of activity suggests it is not currently being worked on. Therefore, it should remain in the backlog for potential future prioritization. medium 2025-05-30 2025-09-10 https://github.com/github/enterprise-primitives/issues/3624
3623 Migrate DB Read Operations to Replicas for `github/github_connect` REST API Endpoints 4: 6mo-1yr 319 217 0 keep becco Keep — Backlog Keep — Backlog The issue is valid and addresses an important scalability concern for the `github/github_connect` REST API endpoints. However, it has been inactive for 217 days, with no recent updates or comments, and no assignees actively working on it. The 'keep' label indicates it is worth retaining, but the lack of activity suggests it is not currently being prioritized. Therefore, it should be kept in the backlog for potential future work. medium 2025-05-30 2025-09-10 https://github.com/github/enterprise-primitives/issues/3623
3622 Migrate DB Read Operations to Replicas for `github/orgs` REST API Endpoints 4: 6mo-1yr 319 217 0 keep becco Keep — Backlog Keep — Backlog The issue is valid and addresses an important scalability concern for the `github/orgs` REST API endpoints. However, it has not been actively worked on for 217 days, and there are no recent comments or assignee activity. The 'keep' label indicates it is worth retaining, but its age and lack of updates suggest it belongs in the backlog rather than active work. medium 2025-05-30 2025-09-10 https://github.com/github/enterprise-primitives/issues/3622
4763 Migrate DB Read Operations to Replicas for `github/teams` REST API Endpoints 4: 6mo-1yr 319 43 0 fanout tracking becco Keep — Active Keep — Backlog The issue is valid and addresses an important optimization for database read operations, as outlined in the detailed body. However, it has not been actively worked on recently (43 days since last update), and there are no comments or assignees indicating immediate progress. The 'fanout tracking' label suggests it is part of a broader initiative but not currently prioritized. Therefore, it should remain in the backlog for future consideration. low 2025-05-30 2026-03-02 https://github.com/github/enterprise-primitives/issues/4763
3650 Initiative: Business , Team, and more Organization orchestrations 4: 6mo-1yr 314 1 3 on track, Initiative mutle, jdennes mutle Keep — Active Keep — Active The issue is labeled 'on track' and 'Initiative,' indicating active work and coordination. It has recent updates (1 day ago) and active engagement from assignees and commenters. Tasks are being tracked, and the rollout plan is under development, showing clear progress and relevance. low 2025-06-05 2026-04-14 https://github.com/github/enterprise-primitives/issues/3650
3655 All tests in `test/integration/stafftools/businesses_controller_test.rb` are skipped in EMU mode 4: 6mo-1yr 313 158 2 keep tchavas Keep — Active Needs Discussion The issue has conflicting perspectives in the comments regarding whether the tests should run in EMU mode or be skipped entirely. The labels and comments indicate that further clarification and discussion are needed to determine the appropriate course of action. Additionally, the issue has been reopened, suggesting it is still relevant but unresolved. medium 2025-06-05 2025-11-07 https://github.com/github/enterprise-primitives/issues/3655
4876 [Bug] Business teams can’t be @ in issues and discussions while their members can 4: 6mo-1yr 310 30 3 bug, inactive, M2 follow up, identity-tnt assyadh Close — Stale Keep — Backlog The issue is valid and addresses a bug related to business team mentions in issues and discussions. While it has been inactive for 30 days and labeled as 'inactive,' it is still relevant and has a 'M2 follow up' label indicating it may be revisited in a future milestone. The comments suggest it is being tracked for later milestones, but no active work is currently underway. Therefore, it should remain in the backlog for potential future prioritization. low 2025-06-09 2026-03-16 https://github.com/github/enterprise-primitives/issues/4876
3678 BusinessUserAccount as source of truth for memberships 4: 6mo-1yr 307 6 2 Stale, not planned mutle Keep — Active Close — Done The issue is labeled as 'done' and the state is 'CLOSED (NOT_PLANNED)', indicating that the work has been completed or deemed unnecessary. Additionally, the checklist in the body shows that most tasks have been addressed, and there is no indication of active work or further updates required. The recent comments do not suggest any unresolved concerns, confirming that the issue can be considered resolved. low 2025-06-12 2026-04-09 https://github.com/github/enterprise-primitives/issues/3678
3754 [Feature Request] Unsuspend installations on soft-delete restoration 4: 6mo-1yr 286 181 1 Feature Request, backlog, keep joshuawalker Keep — Backlog Keep — Backlog The issue is labeled as 'Feature Request' and 'backlog,' indicating it is valid and worth keeping but not actively being worked on. The last update was 181 days ago, and the recent comment confirms it has been triaged as low priority and added to the backlog for future consideration. There is no indication that the issue is stale or resolved, so it should remain in the backlog. medium 2025-07-03 2025-10-16 https://github.com/github/enterprise-primitives/issues/3754
4875 [Internal Feedback] Dashboard "Your teams" section does not include enterprise teams 4: 6mo-1yr 279 30 1 internal feedback, M2 follow up, identity-tnt jdennes Keep — Active Keep — Backlog The issue is valid and highlights a potential gap in functionality regarding enterprise teams not being displayed in the 'Your teams' section of the dashboard. It has relevant code references and a recent comment indicating ongoing interest in the issue. However, there is no evidence of active work or recent assignment, and the 'M2 follow up' label suggests it is intended for future consideration. Therefore, it should be kept in the backlog for potential prioritization later. low 2025-07-10 2026-03-16 https://github.com/github/enterprise-primitives/issues/4875
4730 Logging and product docs content missing for the GitHub teams "request to join" feature 4: 6mo-1yr 277 49 2 documentation, support-escalation, support-sev3 stacycarter Keep — Active Keep — Backlog The issue is valid and addresses missing documentation and logging for a feature that impacts multiple GitHub products, including GitHub Enterprise Server and GitHub.com. While it has not been updated in 49 days, it is labeled as 'support-escalation' and 'documentation,' indicating its importance for customer support and product clarity. The severity level (sev3) suggests it is not urgent but still requires attention. Additionally, recent comments show engagement and agreement on the need for improved documentation, making it worth keeping in the backlog for future prioritization. low 2025-07-11 2026-02-25 https://github.com/github/enterprise-primitives/issues/4730
3982 [from Support] Unable to dismiss Copilot Access requests if CB is `Disabled` 4: 6mo-1yr 269 37 7 support-escalation, support-sev2, keep EboniLM Keep — Active Needs Discussion The issue involves a limitation in the implementation of the 'request access' feature, which has sparked confusion and complaints from multiple customers. Comments indicate uncertainty about the rationale for dismissing Copilot Access requests when Copilot is disabled, and there is disagreement about whether this is a bug or a feature request. Additionally, the issue has been flagged for prioritization and coordination with Product, suggesting that further discussion is needed to clarify the scope and next steps. Labels like 'support-escalation' and 'support-sev2' also highlight the importance of resolving this issue, but no active work is currently underway. medium 2025-07-20 2026-03-09 https://github.com/github/enterprise-primitives/issues/3982
3937 Apps using user authentication should honor GitHub App IP Allow list 4: 6mo-1yr 268 107 17 Feature Request, support-sev2, keep gm3dmo Keep — Active Needs Discussion The issue has a 'Feature Request' label and involves a support escalation with significant customer impact, as indicated by the 'support-sev2' label. Recent comments suggest ongoing discussions about implementation approaches and customer expectations, but no clear resolution or decision has been made yet. The presence of multiple stakeholders and active engagement indicates that further clarification and alignment are required before proceeding. medium 2025-07-21 2025-12-29 https://github.com/github/enterprise-primitives/issues/3937
4761 Optimize group-syncer `list_group_members` endpoint 4: 6mo-1yr 266 44 0 fmacar3na Keep — Active Keep — Backlog The issue is valid and describes a clear optimization need for the `list_group_members` endpoint to address performance concerns with large external group teams. While the first part of the optimization has been completed, the second part remains unaddressed. However, there has been no recent activity (last update was 44 days ago), no assignees, and no comments, indicating it is not actively being worked on. The issue is worth keeping in the backlog for future prioritization. low 2025-07-23 2026-03-02 https://github.com/github/enterprise-primitives/issues/4761
3884 [Feature Request]: Publish hydro event for enterprise delete/restore/susbend/unsuspend/destroy 4: 6mo-1yr 253 48 0 Feature Request, keep TingluoHuang Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed solution for introducing enterprise-level hydro events. It has been open for 253 days with no recent activity (last update 48 days ago) and no comments or assignees. Given its nature as a feature request and lack of active work, it should be closed and tracked through the feature request process. medium 2025-08-05 2026-02-26 https://github.com/github/enterprise-primitives/issues/3884
3879 Enterprise CI suite runs test that don't make sense in enterprise mode 4: 6mo-1yr 253 154 0 keep, tech debt mutle Keep — Active Keep — Backlog The issue is labeled as 'tech debt' and 'keep,' indicating it is still considered valid and worth addressing. However, there has been no recent activity (last updated 154 days ago), and no assignees or comments suggest active work. Given its age and lack of engagement, it is appropriate to place this issue in the backlog for potential future prioritization. medium 2025-08-05 2025-11-12 https://github.com/github/enterprise-primitives/issues/3879
3914 Bug: `MultiTenantProvisioningRequest` not destroyed on Proxima enterprise destruction 4: 6mo-1yr 246 223 2 bug, keep jdennes Keep — Backlog Keep — Backlog The issue is labeled as 'bug' and 'keep,' indicating it is valid and worth retaining. Although it has been open for 246 days with no updates in the last 223 days, the comments suggest that manual intervention was required to address the immediate problem, but further investigation is needed to understand and fix the root cause. This suggests the issue is still relevant but not actively being worked on, making it suitable for the backlog. medium 2025-08-12 2025-09-04 https://github.com/github/enterprise-primitives/issues/3914
4874 [Bug] User is able to create a team named "teams" in an organisation 4: 6mo-1yr 245 30 1 bug, identity-tnt DeraUchenwoke Keep — Active Keep — Backlog The issue is valid and describes a clear bug related to reserved words in team names, which can cause a 404 error. It has relevant context, including reproduction steps and links to related discussions. Although it has not been updated in 30 days and lacks active assignees, the presence of comments from stakeholders (e.g., docs team) indicates ongoing interest. The 'bug' label further supports its validity, but there is no evidence of active work, making it suitable for the backlog. low 2025-08-13 2026-03-16 https://github.com/github/enterprise-primitives/issues/4874
3933 Epic: Migrate Business tasks to use orchestrations 4: 6mo-1yr 244 1 0 epic, on track, keep jdennes jdennes Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and progress. It was updated just 1 day ago, showing recent engagement. Additionally, the assignee is actively working on tasks, as evidenced by the numerous completed subtasks listed in the body. This issue is clearly still relevant and in-progress. medium 2025-08-14 2026-04-14 https://github.com/github/enterprise-primitives/issues/3933
4721 Add datadog panel showing team-sync group activations 4: 6mo-1yr 232 49 2 on track stves Keep — Active Keep — Active The issue has the 'on track' label, indicating active work or prioritization. Additionally, there have been recent comments within the last two months discussing implementation details and related changes, showing ongoing engagement. The issue is still open and relevant, as it addresses a useful enhancement to monitoring capabilities. low 2025-08-26 2026-02-24 https://github.com/github/enterprise-primitives/issues/4721
4890 [Task] Investigate why deleting many teams at once enqueues a lot of jobs into the Copilot job queue 4: 6mo-1yr 232 30 2 on track, task, identity-tnt Strombon Keep — Active Keep — Backlog The issue is still open and has the 'on track' label, indicating it is valid and relevant. However, the recent comment suggests that optimizing the Copilot jobs is no longer a priority, and there has been no activity in the last 30 days. This suggests that the issue is not actively being worked on but should remain in the backlog for potential future prioritization. low 2025-08-25 2026-03-16 https://github.com/github/enterprise-primitives/issues/4890
3980 [MAS C* Remediation Required] MAS grade is D for github/move_work 4: 6mo-1yr 231 55 3 not planned erikaxu, baturn app/accessibility-bot-app Keep — Active Keep — Backlog The issue is valid and pertains to achieving MAS C* compliance for the `github/move_work` service, which aligns with GitHub's accessibility goals. While the issue has been reopened and has recent comments (55 days ago), the team has indicated that this service is not currently the focus of active work, as efforts are prioritized on larger services like `github/enterprise_accounts`. The 'not planned' label further supports that this issue is not actively being worked on but remains relevant for future remediation efforts. low 2025-08-27 2026-02-19 https://github.com/github/enterprise-primitives/issues/3980
4003 [CpL] Update `BasicEnterpriseAccessReinstatementJob` to handle Copilot reinstatement for Business Te 4: 6mo-1yr 225 53 3 not planned therzka lildude Keep — Active Keep — Active The issue is reopened and has recent engagement, including comments confirming its relevance and necessity. The assignee, therzka, has indicated that the issue is not stale, and there is confirmation from related discussions and linked issues that the work still needs to be done. Despite its age, the activity level and clear relevance justify keeping it active. low 2025-09-02 2026-02-21 https://github.com/github/enterprise-primitives/issues/4003
4029 Epic: More Organization orchestrations 4: 6mo-1yr 217 8 0 epic, on track, keep jdennes jdennes Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and relevance. It has been updated recently (8 days ago), and the assignee is actively engaged. Several tasks within the issue are marked as completed, while others remain open, showing ongoing progress. These signals suggest the issue is actively being worked on and should remain open. medium 2025-09-10 2026-04-07 https://github.com/github/enterprise-primitives/issues/4029
4751 Bug: The organization’s team members view does not adjust properly on small screen sizes 4: 6mo-1yr 202 47 5 bug, on track adrianchiran Keep — Active Keep — Active The issue is labeled as 'on track,' indicating active work is being done. Recent comments (47 days ago) show ongoing engagement, including discussions about design drafts and task clarifications. The issue is still open and relevant, with clear next steps outlined for resolution. These signals suggest the issue is actively being worked on and should remain in the 'Keep — Active' bucket. low 2025-09-25 2026-02-27 https://github.com/github/enterprise-primitives/issues/4751
4573 🚧 [Placeholder] Initiative: Enterprise Container Dormancy Reports 4: 6mo-1yr 196 71 0 erikaxu Keep — Active Keep — Backlog The issue is open and describes a valid initiative to provide enterprise container dormancy reports, which aligns with GitHub's goals of optimizing resource usage and improving user experience. However, there has been no recent activity (last update was 71 days ago), no assignees, and no comments, indicating it is not actively being worked on. The absence of 'on track' or similar labels further supports placing this issue in the backlog for potential future prioritization. low 2025-10-01 2026-02-03 https://github.com/github/enterprise-primitives/issues/4573
4110 Previously removed (`unaffiliated`) users unable to be re-added as outside collaborators 4: 6mo-1yr 196 82 11 support-escalation, support-sev2 lildude, raymondtiu, robert-crandall adamrr724 Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case. It has recent engagement from multiple assignees, including comments discussing investigation and a related PR to address part of the problem. Additionally, there are references to ongoing work and documentation updates required once the issue is resolved. These signals suggest the issue is actively being worked on and remains relevant. low 2025-10-01 2026-01-22 https://github.com/github/enterprise-primitives/issues/4110
4871 Enterprise Teams (v2) Scale: Customer Feedback 4: 6mo-1yr 190 28 20 identity-tnt erikaxu Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent updates (28 days ago) and ongoing discussions in the comments about scaling limits and customer feedback. The labels ('identity-tnt') and detailed tracking of scale targets indicate that this issue is still relevant and in-progress, with a clear focus on enabling Enterprise Teams for GHES 3.20 and addressing customer concerns. low 2025-10-07 2026-03-18 https://github.com/github/enterprise-primitives/issues/4871
4867 🚧 [Initiative] Enterprise Teams can have child/nested teams 4: 6mo-1yr 189 30 0 identity-tnt erikaxu Keep — Active Keep — Backlog The issue is valid and outlines a significant feature enhancement for enterprise teams, including detailed scenarios, tasks, and rollout plans. However, it has not been actively worked on recently (last update was 30 days ago), has no assignees, and no recent comments or activity. The 'identity-tnt' label suggests it is part of a broader initiative but not currently prioritized. Therefore, it should remain in the backlog for potential future work. low 2025-10-08 2026-03-16 https://github.com/github/enterprise-primitives/issues/4867
4868 [Initiative] Admins can target ETs directly or by property within policies and rulesets 4: 6mo-1yr 189 30 0 Initiative, identity-tnt erikaxu Keep — Active Keep — Backlog The issue is open and labeled as 'Initiative' and 'identity-tnt,' indicating it is part of a broader workstream. While it has not been updated in 30 days, the detailed description, impact, and tasks suggest it is still valid and worth keeping for future prioritization. There is no recent activity or assignee engagement to suggest it is actively being worked on, so it fits best in the backlog for now. low 2025-10-08 2026-03-16 https://github.com/github/enterprise-primitives/issues/4868
4140 Epic: Appropriate warnings for Enterprise teams that contain outside collaborators 4: 6mo-1yr 189 89 5 epic maiix, raymondtiu, erikaxu raymondtiu Keep — Active Needs Discussion The issue has a 'Stale' label and has been paused by the assignee, but it remains open and has recent comments indicating ongoing interest and questions from stakeholders. Additionally, the issue involves design decisions and product implications, as evidenced by the 'epic' label and references to Figma designs and feature flags. Further discussion is needed to clarify the next steps and validate the approach before deciding on its status. low 2025-10-08 2026-01-16 https://github.com/github/enterprise-primitives/issues/4140
4869 [Initiative] Properties for Enterprise Teams 4: 6mo-1yr 189 30 0 Initiative, identity-tnt erikaxu Keep — Active Keep — Backlog The issue is valid and outlines a clear initiative to enhance Enterprise Teams with properties functionality, which aligns with customer feedback and has a detailed description of tasks and impact. However, there has been no recent activity in the past 30 days, no assignees, and no comments, indicating it is not actively being worked on. The 'Initiative' label further suggests it is part of a broader effort that may be picked up later, making 'Keep — Backlog' the appropriate bucket. low 2025-10-08 2026-03-16 https://github.com/github/enterprise-primitives/issues/4869
4870 [Inititative] Non-admin users can create and maintain enterprise teams 4: 6mo-1yr 189 30 0 identity-tnt erikaxu Keep — Active Keep — Backlog The issue is valid and outlines a clear initiative to enable non-admin users to create and maintain enterprise teams, which could improve administrative delegation and team management. However, it has been open for 189 days with no recent updates in the last 30 days, and there are no active assignees or comments indicating immediate work. The 'identity-tnt' label suggests it is related to identity and team management, which remains relevant but is not actively being worked on. Therefore, it should be kept in the backlog for future prioritization. low 2025-10-08 2026-03-16 https://github.com/github/enterprise-primitives/issues/4870
4259 [Epic] New Enterprise Setting for VS Code Private Marketplace 4: 6mo-1yr 188 22 17 design needed, epic, on track lildude, durfee erikaxu Keep — Active Keep — Active The issue is labeled 'on track' and 'design needed,' indicating active work and pending design decisions. Recent comments from assignees show ongoing activity, including updates on API endpoints and UI fixes. Although the issue was reopened for operational visibility, it remains relevant as the formal release is scheduled for early March. The timeline and recent engagement suggest it is actively being worked on. low 2025-10-09 2026-03-24 https://github.com/github/enterprise-primitives/issues/4259
4872 Bug: Unable to invite enterprise team as a collaborator on the project board 4: 6mo-1yr 181 30 2 bug, M2 follow up, identity-tnt fmacar3na Keep — Active Needs Discussion The issue has labels such as 'M2 follow up' and 'identity-tnt,' indicating it is tied to a specific milestone or team focus. Recent comments suggest uncertainty about whether the described behavior is intentional or tied to feature scope decisions for public preview or GA. This ambiguity requires further discussion to clarify whether this is a bug or an expected limitation based on product decisions. low 2025-10-16 2026-03-16 https://github.com/github/enterprise-primitives/issues/4872
4193 Bug: Soft-deleted EAs aren't always being purged and we're not reporting why 5: <6mo 176 78 1 bug lildude Keep — Active Needs Discussion The issue highlights multiple problems with the `DestroyBusinessJob` logic and raises questions about its design and implementation. The comments suggest dissatisfaction with the current approach and propose potential changes, but no clear resolution or next steps have been defined. Additionally, the issue has been open for 176 days with limited recent activity, indicating that further discussion is needed to clarify the path forward before any action can be taken. low 2025-10-21 2026-01-27 https://github.com/github/enterprise-primitives/issues/4193
4213 Epic: Copilot experience post-launch clean up 5: <6mo 173 70 2 epic, not planned AnthonyLaye Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'not planned,' indicating it is a valid but not actively worked-on task. It was reopened recently and has had some engagement within the last 70 days, suggesting it is still relevant but not urgent. Therefore, it belongs in the backlog for potential future prioritization. low 2025-10-24 2026-02-04 https://github.com/github/enterprise-primitives/issues/4213
4866 [Design] Properties for Enterprise Teams 5: <6mo 160 30 0 identity-tnt adrianchiran Keep — Active Needs Discussion The issue is open and relatively recent (160 days old), with the last update occurring 30 days ago. It references ongoing design work and customer feedback, indicating that the topic is still relevant. However, there are no comments or assignees, and the 'identity-tnt' label suggests it may require further clarification or alignment before progressing. Additional discussion is needed to determine next steps and prioritize this work. low 2025-11-06 2026-03-16 https://github.com/github/enterprise-primitives/issues/4866
4865 [Epic] 🚧 [Epic] Soft delete and restoration window for Enterprise Teams 5: <6mo 159 30 0 enhancement, epic, identity-tnt erikaxu Keep — Active Keep — Backlog The issue is valid and outlines a detailed enhancement proposal for implementing a soft delete and restoration feature for Enterprise Teams. It has the 'enhancement' and 'epic' labels, indicating it is a significant feature request. While the issue is open and relatively recent (159 days old), there has been no activity in the last 30 days, and no assignees or comments suggest active work. Therefore, it should be kept in the backlog for potential future prioritization. low 2025-11-07 2026-03-16 https://github.com/github/enterprise-primitives/issues/4865
4284 Logging issue - Not enough fields exposed for business.remove_member events to help enterprise owner 5: <6mo 156 53 2 support-escalation, support-sev3 stacycarter Keep — Active Needs Discussion The issue is a support escalation labeled as 'support-sev3,' indicating it requires attention but does not have active assignees or recent updates. The comments suggest ongoing clarification about the scope of the requested changes (e.g., exposing 'reason' and 'referrer' fields in logs). Further discussion is needed to finalize the requirements and determine next steps, as the issue's resolution is not yet clear. low 2025-11-10 2026-02-20 https://github.com/github/enterprise-primitives/issues/4284
4282 Bug: Enterprise owners see option to make a user an unaffiliated member in 2 scenarios where it does 5: <6mo 156 34 6 bug, support-escalation, support-sev3 stacycarter Keep — Active Keep — Active The issue is labeled as 'bug' and 'support-escalation', indicating it is a priority for resolution. It is also marked as 'support-sev3', which requires engineering response within one week. The issue has recent engagement, with comments discussing potential solutions and clarifications within the last 34 days. This suggests active work or consideration is ongoing, making it relevant and in-progress. low 2025-11-10 2026-03-12 https://github.com/github/enterprise-primitives/issues/4282
4864 General Enterprise teams feedback 5: <6mo 154 30 0 identity-tnt adrianchiran Keep — Active Keep — Backlog The issue contains valid feedback regarding the enterprise teams experience, with actionable suggestions for improvement. While one item has been marked as fixed, the remaining feedback points are still relevant and unresolved. The issue is open, has a label indicating its relevance to identity-tnt, and has been updated relatively recently (30 days ago). However, there is no active engagement or assignee activity, suggesting it is not currently being worked on but should be kept for future prioritization. low 2025-11-12 2026-03-16 https://github.com/github/enterprise-primitives/issues/4864
4293 [github/enterprise_accounts] [dotcom] [businesses_member_invitations#show] [HPC] Web Performance Sco 5: <6mo 154 1 0 blkdm0n app/web-systems-bot Keep — Active Keep — Active The issue is actively maintained by a robot that reopens it if findings persist, and it was updated just 1 day ago. Additionally, it has an assigned owner (blkdm0n) and includes actionable items with a due date in the future (2026-05-25). These signals indicate that the issue is still relevant and being worked on. low 2025-11-12 2026-04-14 https://github.com/github/enterprise-primitives/issues/4293
4308 🚧 Initiative: Direct-to-Paid Provisioning 5: <6mo 151 133 1 design needed, Initiative erikaxu erikaxu Needs Discussion Needs Discussion The issue is labeled 'design needed' and 'Initiative,' indicating that it is in the early stages of planning and requires further discussion and clarification. The body of the issue outlines a high-level overview and value proposition but lacks detailed responses for key insights, target customers, strategic opportunities, and risks. Additionally, the recent comment from the assignee confirms that the initiative is still in the 'shaping' status and funding is not yet committed, further supporting the need for discussion before moving forward. low 2025-11-14 2025-12-03 https://github.com/github/enterprise-primitives/issues/4308
4330 Bug: Trial activations form incorrectly handling Azure as a purchase 5: <6mo 148 6 1 bug, Stale brandonrosage Keep — Active Close — Stale The issue is marked as 'Stale' and 'not planned,' indicating it is no longer being actively worked on or considered for resolution. Additionally, the state is 'CLOSED (NOT_PLANNED)' and there has been minimal recent activity, with only one comment in the last 6 days. These signals strongly suggest the issue is outdated and no longer relevant. low 2025-11-18 2026-04-09 https://github.com/github/enterprise-primitives/issues/4330
4499 Initiative: Introduce In-product Safeguard Limits Across the Enterprise Platform 5: <6mo 148 6 23 blocked, enhancement, on track, Initiative wallace, jdennes, erikaxu jackieytan Keep — Active Keep — Active The issue is labeled 'on track' and has recent updates, including comments and progress summaries within the last week. It is actively being worked on, with assigned contributors and a clear target date of 2026-05-27. Additionally, the initiative's deliverables and progress are well-documented, indicating ongoing engagement and relevance. low 2025-11-18 2026-04-09 https://github.com/github/enterprise-primitives/issues/4499
4750 Include original actor ID and requestor ID details on retry jobs 5: <6mo 141 34 3 support-escalation, support-sev3, on track FreezerB Keep — Active Keep — Active The issue is labeled 'support-escalation', 'support-sev3', and 'on track', indicating active work and prioritization. Recent comments show ongoing discussion about a draft PR and potential fixes, with contributors engaging within the last 34 days. The issue remains open and relevant, as it addresses a customer-impacting problem for AT&T. These signals suggest the issue is actively being worked on and should remain in the active bucket. low 2025-11-24 2026-03-12 https://github.com/github/enterprise-primitives/issues/4750
4349 Task: Put back legal disclaimer for Copilot use 5: <6mo 140 42 0 task, not planned AnthonyLaye Keep — Active Keep — Backlog The issue is valid and pertains to adding a legal disclaimer to the new Copilot licensing page, which is important for compliance. However, the 'not planned' label and lack of recent activity or assignee suggest that it is not actively being worked on at the moment. It should remain in the backlog for potential future prioritization. low 2025-11-25 2026-03-04 https://github.com/github/enterprise-primitives/issues/4349
4397 Initiative: Classify and fulfill Data Subject Requests (DSR) for mEAO services 5: <6mo 128 72 4 inactive, Initiative AnthonyLaye AnthonyLaye Close — Stale Close — Stale The issue has been marked as 'inactive' and the last update indicates that no further work is required from the team at this time. Additionally, there has been no meaningful activity for 72 days, and the initiative appears to have reached a point where the team's involvement is complete unless circumstances change. Keeping this issue open is unnecessary given its current state. low 2025-12-08 2026-02-02 https://github.com/github/enterprise-primitives/issues/4397
4716 Prevent duplicate enqueues for group-syncer 5: <6mo 127 50 3 incident-repair, incident-repair-long-term fmacar3na Keep — Active Keep — Active The issue is labeled with 'incident-repair' and 'incident-repair-long-term,' indicating it is part of a prioritized repair effort stemming from an availability review. Recent comments (50 days ago) suggest active engagement and prioritization, with contributors discussing potential solutions and referencing related incidents. The issue is still open and relevant, with actionable options outlined in the body. These signals suggest it is actively being worked on or monitored. low 2025-12-09 2026-02-24 https://github.com/github/enterprise-primitives/issues/4716
4741 Bug: Org team add members UI is showing enterprise team members in EMU 5: <6mo 126 47 0 bug fmacar3na Keep — Active Keep — Backlog The issue describes a valid bug in the UI behavior for enterprise team members in EMU, and it has detailed reproduction steps and screenshots. However, there has been no recent activity (last update was 47 days ago), no assignees, and no comments indicating active work. The 'bug' label suggests it is worth keeping for future prioritization, but it is not actively being worked on at the moment. low 2025-12-10 2026-02-27 https://github.com/github/enterprise-primitives/issues/4741
4416 [github/orgs] Accessibility Violations Tracking Issue 🧰 5: <6mo 124 14 4 done baturn app/accessibility-bot-app Close — Done Keep — Active The issue is actively being worked on, as evidenced by recent comments from assignees and updates within the last 14 days. Although labeled 'done,' the issue remains open and is maintained by automated systems that reopen it when new violations are detected. This indicates ongoing relevance and active monitoring. high 2025-12-12 2026-03-31 https://github.com/github/enterprise-primitives/issues/4416
4860 Add retries for classified retryable errors 5: <6mo 119 30 0 identity-tnt DeraUchenwoke Keep — Active Keep — Backlog The issue is still open and has a clear dependency on another issue (#4861), indicating it is valid and worth keeping. However, there has been no recent activity in the last 30 days, and no assignees are currently working on it, suggesting it is not actively being worked on at the moment. The 'identity-tnt' label further supports its relevance to the project backlog. low 2025-12-17 2026-03-16 https://github.com/github/enterprise-primitives/issues/4860
4861 Differentiate retryable and non-retryable Team Sync errors 5: <6mo 119 30 0 identity-tnt DeraUchenwoke Keep — Active Keep — Backlog The issue is valid and outlines specific tasks to differentiate retryable and non-retryable Team Sync errors. It is dependent on another issue (#4862), which suggests it is part of a broader effort. However, there has been no recent activity in the past 30 days, no assignees, and no comments, indicating it is not actively being worked on. The 'identity-tnt' label further supports its relevance to the repository's scope, making it suitable for the backlog. low 2025-12-17 2026-03-16 https://github.com/github/enterprise-primitives/issues/4861
4862 Raise exceptions for Team Sync install failures on new orgs 5: <6mo 119 30 0 identity-tnt DeraUchenwoke Keep — Active Keep — Backlog The issue is valid and outlines specific steps to address a problem with team sync failures for new organizations. It is labeled 'identity-tnt,' indicating it is relevant to the team's scope. However, there has been no recent activity in the last 30 days, no assignees, and no comments, suggesting it is not actively being worked on. It should remain in the backlog for future prioritization. low 2025-12-17 2026-03-16 https://github.com/github/enterprise-primitives/issues/4862
4739 [Batch] Missing organization team sync app installation 5: <6mo 119 47 0 batch DeraUchenwoke Keep — Active Keep — Backlog The issue describes a valid bug related to the team sync application missing in certain scenarios. It has been open for 119 days with no recent updates in the last 47 days, and there are no assignees or active engagement. The 'batch' label suggests it is part of a larger set of issues, but it is not actively being worked on. Therefore, it should be kept in the backlog for future prioritization. low 2025-12-17 2026-02-26 https://github.com/github/enterprise-primitives/issues/4739
4863 Add support for multiple Copilot policies (1 per enterprise-team) 5: <6mo 118 30 6 identity-tnt shakerg Keep — Active Needs Discussion The issue presents a detailed problem and proposed solution regarding Copilot policies for Copilot-Standalone enterprises, but there are unresolved questions and clarifications needed based on the comments. Specifically, there is ongoing discussion about the scope of the request (enterprise teams vs. Copilot policy behavior) and who should be involved in addressing it. The presence of active engagement and the 'identity-tnt' label further indicate that this issue requires additional discussion before a clear path forward can be determined. low 2025-12-17 2026-03-16 https://github.com/github/enterprise-primitives/issues/4863
4434 Confusion for trial enterprises adding payment method - leading to early trial cancellation, uninten 5: <6mo 117 44 9 support-escalation, support-sev3, product decision anna-talley Keep — Active Needs Discussion The issue has the 'product decision' label, indicating that further discussion is required to determine the appropriate course of action. Additionally, the issue is a support escalation with multiple examples of customer confusion and impact, suggesting that a resolution requires input from relevant stakeholders. While the issue is active with recent comments, no clear resolution or next steps have been identified, necessitating further discussion. low 2025-12-18 2026-03-02 https://github.com/github/enterprise-primitives/issues/4434
4443 Epic: [Enterprise IA] Integrations Section 5: <6mo 114 6 0 epic, Stale kfrank, durfee, martagodoy kfrank Keep — Active Close — Stale The issue is marked as 'Stale' and 'not planned,' indicating that it is no longer actively being worked on or considered. It has been closed with the state 'NOT_PLANNED,' and there has been no meaningful activity or comments in the past 114 days. These signals strongly suggest that the issue is outdated and no longer relevant. low 2025-12-22 2026-04-09 https://github.com/github/enterprise-primitives/issues/4443
4442 Epic: [Enterprise IA] Organizations and Repositories Restructure 5: <6mo 114 7 3 epic, on track martagodoy kfrank Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and prioritization. It has recent updates (7 days ago) and ongoing engagement from assignees and commenters, including progress updates and target dates. The presence of active PRs and a clear roadmap further supports its relevance and active status. low 2025-12-22 2026-04-08 https://github.com/github/enterprise-primitives/issues/4442
4441 Epic: [Enterprise IA] Code integrity Section 5: <6mo 114 6 0 epic, Stale kfrank, durfee, martagodoy kfrank Keep — Active Close — Stale The issue is marked as 'Stale' and 'not planned,' indicating that it is no longer actively being worked on or prioritized. Additionally, the issue is closed with no recent meaningful activity or comments in the last 6 days, and it has been inactive for over 3 months. These signals strongly suggest that the issue is outdated and no longer relevant. low 2025-12-22 2026-04-09 https://github.com/github/enterprise-primitives/issues/4441
4440 Epic: [Enterprise IA] GA 5: <6mo 114 15 0 epic, not planned kfrank, durfee, martagodoy kfrank Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'not planned,' indicating it is a valid long-term initiative but not actively being worked on. It has been reopened and updated recently (15 days ago), showing some level of engagement. However, there are no recent comments or active progress, suggesting it belongs in the backlog for future prioritization. low 2025-12-22 2026-03-31 https://github.com/github/enterprise-primitives/issues/4440
4439 Epic: [Enterprise IA] Public Preview 5: <6mo 114 15 0 epic, not planned kfrank, durfee, martagodoy kfrank Keep — Active Keep — Active The issue is labeled as 'epic' and has active assignees, indicating ongoing work. It was updated recently (15 days ago), suggesting it is still relevant and being worked on. Despite the 'not planned' label, the presence of tasks and assignees signals active engagement. low 2025-12-22 2026-03-31 https://github.com/github/enterprise-primitives/issues/4439
4451 IP Allow List UX and docs improvements to reduce customer security risk 5: <6mo 106 0 5 support-escalation, support-sev3, product decision stacycarter Keep — Active Needs Discussion The issue has the 'product decision' label and multiple comments indicating that product input and confirmation are required before proceeding with any action. Additionally, the issue is tied to a support escalation with a severity level of 3, which suggests it is important but not urgent. The recent activity (last update was today) and ongoing discussion among team members further indicate that the issue requires further clarification and alignment before a resolution can be determined. low 2025-12-30 2026-04-15 https://github.com/github/enterprise-primitives/issues/4451
4889 Intermittent test failure: RepositoryMembershipDependencyTest#test__direct_or_team_member_ids_return 5: <6mo 96 22 16 identity-tnt hubot app/flakes-app Keep — Active Keep — Active The issue is actively being tracked and has recent engagement, including comments from the flakes-app and a recent reopening by hubot. It is marked as flaky and requires resolution to prevent further disruptions in CI builds. The issue is still relevant and has clear next steps outlined for fixing the test. low 2026-01-09 2026-03-24 https://github.com/github/enterprise-primitives/issues/4889
4489 Epic: Support ETv1 to ETv2 team migration in GHES 5: <6mo 92 89 0 epic pndemo Keep — Active Keep — Backlog The issue is labeled as an 'epic' and outlines a significant feature development for migrating ETv1 to ETv2 teams in GHES. While it has not been updated in 89 days and has no recent activity or assignees, the described tasks and impact suggest that it is still relevant and worth keeping for future work. It does not meet criteria for closure as stale or done, nor does it require immediate discussion. low 2026-01-13 2026-01-16 https://github.com/github/enterprise-primitives/issues/4489
4488 Epic: Migration of large basic plan enterprises 5: <6mo 92 0 0 epic, Stale pndemo Keep — Active Close — Stale The issue is labeled as 'Stale' and has had no meaningful activity despite being open for 92 days. There are no comments or assignees, and the last update was on the same day it was marked stale. This suggests the issue is no longer actively pursued or relevant. low 2026-01-13 2026-04-15 https://github.com/github/enterprise-primitives/issues/4488
4487 Epic: Mandatory migration of small basic plan enterprises 5: <6mo 92 89 0 epic pndemo Keep — Active Keep — Backlog The issue is labeled as an 'epic' and outlines a detailed plan for mandatory migration of small basic plan enterprises. Although it has been open for 92 days with no recent updates or comments, the tasks and references indicate that it is still valid and worth keeping for future work. There is no indication that the issue is stale or completed, and it does not require immediate discussion or resolution. Therefore, it should remain in the backlog for potential prioritization later. low 2026-01-13 2026-01-16 https://github.com/github/enterprise-primitives/issues/4487
4502 Restructure CAP logic to check if resources unauthorized for user 5: <6mo 89 20 0 pndemo Keep — Active Keep — Backlog The issue is still open and contains detailed references to ongoing work and dependencies, such as linked PRs and Slack discussions. While some tasks have been completed, others remain unresolved, including updates to authorization and notifications logic. The lack of recent activity (20 days since last update) and no assignees suggest it is not actively being worked on but remains valid and worth keeping for future prioritization. low 2026-01-16 2026-03-26 https://github.com/github/enterprise-primitives/issues/4502
4540 UI: Warn that adding an existing child team re-parents it 5: <6mo 79 64 2 support-escalation, support-sev3, design needed, product decision astropedrito Keep — Active Needs Discussion The issue has the 'design needed' and 'product decision' labels, indicating that further discussion is required to determine the appropriate solution. Additionally, recent comments from team members suggest ongoing engagement and the need for collaboration between product and design teams. While the issue is 79 days old, the presence of these labels and the nature of the comments signal that it is not yet ready for resolution or backlog placement. low 2026-01-26 2026-02-09 https://github.com/github/enterprise-primitives/issues/4540
4539 Epic: Define public interfaces for Enterprise primitives 5: <6mo 79 35 4 epic, on track, inactive mutle mutle Close — Stale Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and prioritization. Although there are periods of inactivity, recent comments from the assignee show ongoing updates and progress, such as metrics tracking and preparatory work dependencies. The target date is set for 2026-06-27, further confirming its relevance and active status. low 2026-01-26 2026-03-11 https://github.com/github/enterprise-primitives/issues/4539
4536 Initiative: Scaling Enterprise primitives 5: <6mo 79 40 4 on track, Initiative wallace mutle Keep — Active Keep — Active The issue is labeled 'on track' and has recent engagement from the assignee, wallace, who has provided detailed updates on progress, blockers, and next steps. The initiative is clearly being actively worked on, with a target date set for 2026-06-30 and multiple completed tasks referenced in the comments. These signals indicate that the issue is still relevant and in-progress. low 2026-01-26 2026-03-06 https://github.com/github/enterprise-primitives/issues/4536
4549 Task: Update broken links on "General" page 5: <6mo 78 78 0 task octoshin Keep — Active Keep — Backlog The issue is valid and describes a task to update broken links, which is worth keeping. However, there has been no activity or updates in 78 days, and it is not actively being worked on. The 'task' label further supports that this is a backlog item rather than an active priority. low 2026-01-27 2026-01-27 https://github.com/github/enterprise-primitives/issues/4549
4548 Task: Update "Profile" to "General" 5: <6mo 78 78 0 task octoshin Keep — Active Close — Stale The issue is 78 days old with no updates or comments since its creation. It appears to be inactive, and there is no indication of ongoing work or recent engagement. Additionally, the referenced PR may have already addressed the task, making this issue potentially outdated. low 2026-01-27 2026-01-27 https://github.com/github/enterprise-primitives/issues/4548
4547 Batch: Display Name GA Launch 5: <6mo 78 78 0 batch, Initiative octoshin Keep — Active Keep — Backlog The issue is valid and outlines a clear feature proposal with significant impact and references to customer feedback and internal documentation. However, it has not been updated or actively worked on in 78 days, and there are no assignees or recent comments indicating active progress. The 'batch' and 'Initiative' labels suggest it is part of a broader initiative but currently in a backlog state. low 2026-01-27 2026-01-27 https://github.com/github/enterprise-primitives/issues/4547
4543 [Feature Request]: Allow customers to customize the sync cadence for Team Sync 5: <6mo 78 65 1 Feature Request, product decision SirHawbly Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and 'product decision,' indicating it is a request for new functionality rather than an active bug or task. It has been open for 78 days with no recent updates (last update was 65 days ago), and the body explicitly mentions this as a feature request to address customer needs. Additionally, the comment suggests it has been removed from the feature request board, further supporting closure and tracking through the feature request process. low 2026-01-27 2026-02-09 https://github.com/github/enterprise-primitives/issues/4543
4568 [Feature Request]: Use blob storage for `team_orchestrations` id list columns 5: <6mo 72 68 3 Feature Request eggyhead Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and proposes a solution for using blob storage for certain columns in the `team_orchestrations` table. There has been no meaningful activity in the last 68 days, and the comments suggest that the table size is small and purged regularly, reducing the urgency of this change. As this is a feature request rather than an active issue, it should be closed and tracked through the feature request process. low 2026-02-02 2026-02-05 https://github.com/github/enterprise-primitives/issues/4568
4579 Batch: Transfer ownership of group-syncer 5: <6mo 71 54 1 batch AnthonyLaye AnthonyLaye Keep — Active Keep — Backlog The issue is open and contains actionable tasks related to the transfer of ownership for the group-syncer service. While there has been no recent activity in the past 54 days, the tasks outlined remain valid and relevant. The presence of an assignee indicates potential future work, but the lack of recent updates suggests it is not actively being worked on at the moment. Therefore, it is appropriate to keep this issue in the backlog for future prioritization. low 2026-02-03 2026-02-20 https://github.com/github/enterprise-primitives/issues/4579
4578 Initiative: Ingestion of Teams services 5: <6mo 71 42 8 epic, on track, Initiative AnthonyLaye AnthonyLaye Keep — Active Keep — Active The issue is labeled as 'on track' and 'Initiative,' indicating active work. Recent comments from the assignee show ongoing updates and progress, including references to completed tasks and remaining work being moved to another epic. The issue is still relevant and actively managed, with a target date mentioned and recent engagement within the last 42 days. low 2026-02-03 2026-03-04 https://github.com/github/enterprise-primitives/issues/4578
4581 Searching for a managed user account on the organization `People` page returns no results 5: <6mo 70 0 30 support-escalation, support-sev3, non-scaling-related deepumrtn Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev3,' indicating it is a priority support case. It has been actively updated, with the last update occurring today and 30 comments showing ongoing engagement. Additionally, recent comments suggest progress is being made, such as deployment of a potential fix and requests for customer feedback. These signals indicate the issue is actively being worked on and remains relevant. low 2026-02-04 2026-04-15 https://github.com/github/enterprise-primitives/issues/4581
4593 Batch: Write a transition to handle migration of all ETv1s 5: <6mo 69 69 0 batch AnthonyLaye Keep — Active Keep — Backlog The issue is open and appears to be valid, with specific tasks outlined for handling the migration of ETv1s. However, there has been no activity or updates in 69 days, and no assignees or comments indicating active work. The 'batch' label suggests it is part of a larger batch process, but it is not currently being worked on. Therefore, it should be kept in the backlog for potential future prioritization. low 2026-02-05 2026-02-05 https://github.com/github/enterprise-primitives/issues/4593
4592 Batch: Questions to consider for migration 5: <6mo 69 16 1 batch AnthonyLaye Keep — Active Needs Discussion The issue contains a list of complex questions and considerations related to migration that require input from multiple teams, including product and engineering. The presence of specific questions about API behavior, licensing, and operational risks indicates that further discussion and clarification are needed before actionable steps can be taken. Additionally, the recent comment by the author suggests ongoing thought and refinement of the issue, reinforcing the need for collaborative discussion. low 2026-02-05 2026-03-30 https://github.com/github/enterprise-primitives/issues/4592
4590 Batch: Create a test plan for the ETv1 to ETv2 migration 5: <6mo 69 69 0 batch AnthonyLaye Keep — Active Keep — Backlog The issue is valid and outlines a checklist for the ETv1 to ETv2 migration test plan, which is important for ensuring a successful migration. However, there has been no activity or updates in 69 days, and no assignees or comments indicate active work. The 'batch' label suggests it is part of a larger effort but not currently prioritized, making it suitable for the backlog. low 2026-02-05 2026-02-05 https://github.com/github/enterprise-primitives/issues/4590
4588 Feature Flag Fundamental Tracking 5: <6mo 69 65 0 AnthonyLaye AnthonyLaye Keep — Active Keep — Backlog The issue is open and appears to be valid, with a clear list of tasks related to feature flag cleanup. However, there has been no activity for 65 days, and no recent comments or updates suggest active work. The presence of an assignee indicates potential future action, but the lack of engagement places it in the backlog for now. low 2026-02-05 2026-02-09 https://github.com/github/enterprise-primitives/issues/4588
4654 Epic: A11y Tracking for Enterprise Primitives 5: <6mo 64 21 6 epic, on track blkdm0n blkdm0n Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and progress. It has recent updates (last updated 21 days ago) and multiple comments showing ongoing engagement from the assignee and contributors. Additionally, the body and comments detail specific tasks and updates, confirming that the issue is still relevant and actively being worked on. low 2026-02-10 2026-03-24 https://github.com/github/enterprise-primitives/issues/4654
4658 Epic: Automate KTLO for group-syncer 5: <6mo 63 63 0 epic robert-crandall robert-crandall Keep — Active Keep — Backlog The issue is labeled as 'epic' and outlines a detailed plan for automating KTLO for the group-syncer repository. Although it has not been updated in 63 days and has no comments, it remains open and assigned to an individual, indicating it is still valid and worth keeping. However, there is no evidence of active work or recent engagement, suggesting it belongs in the backlog for future prioritization. low 2026-02-11 2026-02-11 https://github.com/github/enterprise-primitives/issues/4658
4671 [Internal Feedback] Organization icon on people page is inaccurate and lacks on-hover affordance 5: <6mo 62 26 4 internal feedback gmondello Keep — Active Keep — Backlog The issue is valid and has been acknowledged as part of a broader redesign effort, as indicated by comments referencing the redesign epic (#4438). While it is not actively being worked on, it remains relevant and should be kept in the backlog for future consideration. The 'internal feedback' label further supports its inclusion in the backlog for prioritization. low 2026-02-12 2026-03-20 https://github.com/github/enterprise-primitives/issues/4671
4837 [Task] Allow repository administrators to unassign ETs they set in their repository 5: <6mo 55 27 1 inactive, task bvennam Close — Stale Close — Stale The issue has been labeled as 'inactive' and has not seen meaningful activity for 27 days. Additionally, there is no indication of active work or recent engagement from assignees or contributors. Given its age of 55 days and lack of updates, it appears to be outdated or no longer relevant. low 2026-02-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4837
4834 [Task] Allow organization owners to unassign ETs they set in their organization 5: <6mo 55 27 1 inactive, task bvennam Close — Stale Close — Stale The issue has been labeled as 'inactive' and has not seen meaningful activity for 27 days. Additionally, there is no evidence of active work or recent engagement from assignees or contributors. Given its age of 55 days and lack of updates, it appears to be stale and should be closed. low 2026-02-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4834
4833 [Task] Allow organization owners to discover and assign enterprise teams to their organization 5: <6mo 55 27 0 inactive, task bvennam Close — Stale Close — Stale The issue has been labeled as 'inactive' and has not seen any meaningful activity or updates in the past 27 days. Additionally, there are no comments or assignees, suggesting that it is not currently being worked on. Given its age of 55 days and lack of engagement, it is appropriate to close this issue as stale. low 2026-02-19 2026-03-18 https://github.com/github/enterprise-primitives/issues/4833
4835 [Task] Org owners can remove a team they added and see which teams require higher permissions to rem 5: <6mo 55 27 2 inactive, task maiix, blkdm0n bvennam Close — Stale Needs Discussion The issue has the 'inactive' label but recent comments indicate active engagement from assignees discussing design requirements and clarifications. Additionally, the presence of the 'needs-design' label suggests that further discussion or input is required before the task can proceed. This signals that the issue is not yet ready for active work and requires more clarification or alignment. low 2026-02-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4835
4832 [Epic] Org & Repo Admins can discover and assign Enterprise Teams to their Resources 5: <6mo 55 21 4 epic, on track, inactive robert-crandall bvennam Close — Stale Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work and prioritization. Recent updates from assignees and contributors, including progress on data model changes and timeline adjustments, confirm ongoing engagement. The target date of 2026-05-15 further supports that this issue is actively being worked on and remains relevant. low 2026-02-19 2026-03-25 https://github.com/github/enterprise-primitives/issues/4832
4708 [Feature Request]: single method of uploading compliance reports to all stamps 5: <6mo 51 51 1 Feature Request khellanp Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and proposes a new functionality for uploading compliance reports across all Proxima stamps. There has been no recent activity or indication that this is actively being worked on, and the comments suggest it is not a priority at this time. Closing it as a feature request ensures it can be tracked through the appropriate process for future consideration. low 2026-02-23 2026-02-23 https://github.com/github/enterprise-primitives/issues/4708
4717 EnterpriseTeamOrganizationReconciliationRunnerJob Lock Storm for SAP 5: <6mo 50 5 33 support-escalation, support-sev2 lildude harricross Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2', indicating it is a high-priority support case. It has recent activity, with comments from both the author and assignee within the last 5 days. The assignee, lildude, is actively engaged in troubleshooting and providing guidance. Additionally, the issue remains open and unresolved, with ongoing discussions about mitigation strategies and potential fixes. These signals suggest the issue is actively being worked on and should remain in the 'Keep — Active' bucket. low 2026-02-24 2026-04-10 https://github.com/github/enterprise-primitives/issues/4717
4737 Internal testing checklist for `basic` to `full` enterprise account transition 5: <6mo 48 33 2 raymondtiu Keep — Active Needs Discussion The issue outlines a detailed internal testing checklist for enterprise account transitions, but it includes open questions and requests for additional input, particularly regarding sales and finance systems. The recent comment from shannonhines suggests further validation is needed, indicating that the issue requires more discussion and clarification before it can proceed. The lack of assignees and the relatively recent activity (33 days ago) further supports the need for continued engagement to finalize the scope and requirements. low 2026-02-26 2026-03-12 https://github.com/github/enterprise-primitives/issues/4737
5065 Customer `AT&T` can't install apps on the `ATT-DP1` organisation due to timeouts 5: <6mo 48 9 9 support-escalation, support-sev2 mcfluffinstein Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority customer-facing problem requiring active attention. Recent comments (9 days ago) show ongoing investigation and ownership clarification, with detailed analysis pointing to scalability issues in business member queries. The issue is still open and relevant, with active engagement from multiple team members, making it appropriate to keep it in the active bucket. low 2026-02-26 2026-04-06 https://github.com/github/enterprise-primitives/issues/5065
4735 [Internal Feedback] Refresh docs links on enterprise "welcome" pages 5: <6mo 48 27 4 product decision, internal feedback isaacmbrown Keep — Active Needs Discussion The issue has the 'product decision' label, indicating that further discussion or clarification is required to determine the best course of action. Additionally, recent comments show active engagement from multiple participants, but no clear resolution or decision has been made yet. The issue involves internal feedback and requires input from a PM to finalize the replacement links, making it appropriate for the 'Needs Discussion' bucket. low 2026-02-26 2026-03-19 https://github.com/github/enterprise-primitives/issues/4735
4740 Query for stale public org member records 5: <6mo 47 47 0 robert-crandall Keep — Active Keep — Backlog The issue is valid and describes a need to query for stale public organization member records, which could have operational implications. However, it has not been updated or actively worked on in 47 days, and there are no assignees or comments indicating active engagement. It should be kept in the backlog for potential future prioritization. low 2026-02-26 2026-02-26 https://github.com/github/enterprise-primitives/issues/4740
4771 Datadog (dd:32159512:751d3a0e07ed0b15) - github/teams/high-5xx-percentage - 2026-03-03 18:49:52 UTC 5: <6mo 43 43 0 datadog, CRITICAL, sev1, catalog_service:github/teams, stamp:dotcom robert-crandall ninesappbot Keep — Active Keep — Active The issue is labeled as 'CRITICAL' and 'sev1', indicating high priority. It is actively assigned to 'robert-crandall' and pertains to a recent Datadog alert about high 5xx error percentages in the github/teams service. Although there has been no activity since its creation 43 days ago, the severity and relevance of the issue suggest it is still actively being monitored or worked on. Closing it would be premature without confirmation of resolution. low 2026-03-03 2026-03-03 https://github.com/github/enterprise-primitives/issues/4771
4768 Local/built-in user(s) not getting added as enterprise members on GHES 5: <6mo 43 42 1 support-escalation, support-sev3 stacycarter Keep — Active Keep — Backlog The issue is a valid support escalation related to GHES functionality and has been reproduced on multiple versions, indicating it is still relevant. However, there has been no meaningful activity or updates in the past 42 days, and no assignees are actively working on it. The 'support-escalation' and 'support-sev3' labels suggest it is important but not urgent, making it suitable for the backlog until prioritized. low 2026-03-03 2026-03-04 https://github.com/github/enterprise-primitives/issues/4768
4766 Epic: References to owning enterprise in models 2/2 5: <6mo 43 7 2 epic, at risk tchavas Keep — Active Keep — Backlog The issue is labeled as 'epic' and 'at risk,' indicating its importance and current challenges. While there has been recent activity (7 days ago), the latest update explicitly states that work on this initiative is on pause due to prioritization of the mysql1 work. The tasks outlined in the issue remain valid and actionable, but the initiative is not actively being worked on at the moment. Therefore, it should be kept in the backlog for future prioritization. low 2026-03-03 2026-04-08 https://github.com/github/enterprise-primitives/issues/4766
4797 Initiative: 2026 Q2 Scheduled FR work 5: <6mo 42 28 3 on track, Initiative blkdm0n wallace Keep — Active Keep — Active The issue is labeled 'on track' and 'Initiative,' indicating active work and alignment with a broader initiative. Recent updates from the assignee (blkdm0n) within the last 28 days show ongoing progress on multiple tasks, including SLO migration and accessibility remediation. The issue is clearly still relevant and actively being worked on. low 2026-03-04 2026-03-18 https://github.com/github/enterprise-primitives/issues/4797
4804 Initiative: Assume "ownership" of GitHub Open Source Terraform Project 5: <6mo 41 41 0 Initiative robert-crandall wallace Keep — Active Keep — Backlog The issue is labeled as 'Initiative,' indicating it is part of a broader effort or project. It is open and has had no updates or comments in 41 days, suggesting it is not actively being worked on at the moment. However, the described initiative is still valid and important, as it involves assuming ownership of a widely used Terraform module with significant impact on EA customers. Therefore, it should be kept in the backlog for future prioritization. low 2026-03-05 2026-03-05 https://github.com/github/enterprise-primitives/issues/4804
4800 Epic: GHEC for Terraform Integration 5: <6mo 41 27 2 epic robert-crandall Keep — Active Keep — Active The issue is labeled as 'epic,' indicating it is a high-level tracking issue for a significant initiative. It has recent activity, with updates and comments from the author within the last 27 days. The issue is clearly still relevant, as it tracks the setup and governance of a GHEC environment for Terraform integration, which has been approved and is actively being worked on. These signals suggest it should remain in the active bucket. low 2026-03-04 2026-03-19 https://github.com/github/enterprise-primitives/issues/4800
4921 [Initiative] Migrate user-related tables from mysql1 to dedicated users cluster 5: <6mo 40 0 23 on track, Initiative, mysql1-load-reduction-plan-daily mutle jmillsy Keep — Active Keep — Active The issue is labeled 'on track' and has frequent updates, with the most recent update occurring today. It is actively being worked on by multiple contributors, including the assignee 'mutle,' and has significant engagement with 23 comments. The initiative is part of a broader plan and has a clear target date of 2026-06-01, indicating ongoing progress and relevance. low 2026-03-06 2026-04-15 https://github.com/github/enterprise-primitives/issues/4921
4810 Enterprise platform safeguard limits release readiness 5: <6mo 40 26 0 jdennes Keep — Active Keep — Backlog The issue is valid and outlines specific tasks required for release readiness, but there has been no recent activity in the past 26 days, and no assignees or comments indicating active work. It does not appear to be actively worked on at the moment, but it remains relevant and should be kept in the backlog for future prioritization. low 2026-03-06 2026-03-19 https://github.com/github/enterprise-primitives/issues/4810
4809 Leverage the newly introduced `business_id` field on `OrganizationInvitation` model 5: <6mo 40 40 0 tchavas Keep — Active Keep — Backlog The issue is valid and outlines specific optimizations that can be made now that the `business_id` field has been introduced. However, there has been no activity or updates in the past 40 days, and no assignees are currently working on it. The absence of recent engagement suggests it is not actively being worked on, but the issue remains relevant and could be picked up later. low 2026-03-06 2026-03-06 https://github.com/github/enterprise-primitives/issues/4809
4808 Epic: Improve the performance of queries by using the newly introduced `business_id` field on key mo 5: <6mo 40 28 0 epic tchavas Keep — Active Keep — Backlog The issue is labeled as an 'epic' and outlines a clear plan for improving query performance using the `business_id` field. Although it has not been updated in 28 days and has no recent activity, it remains relevant and valid as it depends on the completion of other tasks. It should be kept in the backlog for future prioritization. low 2026-03-06 2026-03-17 https://github.com/github/enterprise-primitives/issues/4808
4807 Bug: Enterprise New Organization button is not showing for FGP users 5: <6mo 40 7 3 bug, done robert-crandall robert-crandall Close — Done Keep — Active The issue is labeled as 'done,' but it has been reopened and is actively being worked on, as evidenced by recent comments from both the author and other contributors discussing verification and customer feedback. Additionally, the issue has an assignee, indicating ongoing engagement. The age of the issue (40 days) and recent updates (7 days ago) further support its relevance and active status. high 2026-03-05 2026-04-07 https://github.com/github/enterprise-primitives/issues/4807
4815 Leverage the newly introduced `business_id` field on `ExternalGroupTeam` model 5: <6mo 39 39 0 tchavas Keep — Active Keep — Backlog The issue is valid and outlines specific optimization opportunities related to the `business_id` field on the `ExternalGroupTeam` model. However, it has not been updated or actively worked on in 39 days, and there are no assignees or comments indicating immediate progress. Given its relevance and potential impact, it should be kept in the backlog for future prioritization. low 2026-03-07 2026-03-07 https://github.com/github/enterprise-primitives/issues/4815
4814 Leverage the newly introduced `business_id` field on `ExternalGroup` model 5: <6mo 39 36 1 tchavas Keep — Active Keep — Backlog The issue is open and describes valid optimization opportunities for leveraging the newly introduced `business_id` field on the `ExternalGroup` model. While it has not been updated in the past 36 days, the detailed analysis and proposed changes indicate that the issue is still relevant and worth keeping for future work. There is no indication of active work or recent engagement, so it fits best in the backlog for potential prioritization later. low 2026-03-07 2026-03-10 https://github.com/github/enterprise-primitives/issues/4814
4813 Bug: GraphQL `RemoveEnterpriseMember` fails on large enterprises 5: <6mo 39 39 0 bug robert-crandall Keep — Active Keep — Backlog The issue describes a valid bug with the `RemoveEnterpriseMember` GraphQL mutation failing for large enterprises due to query limits. It is relatively recent (39 days old) and has not been updated or actively worked on yet, but the detailed analysis and proposed solution indicate it is worth keeping for future prioritization. The absence of assignees or recent activity suggests it is not currently being worked on, making 'Keep — Backlog' the appropriate bucket. low 2026-03-06 2026-03-06 https://github.com/github/enterprise-primitives/issues/4813
4820 Epic: Testing and bug fixes for ETv1 -> ETv2 migration 5: <6mo 37 4 6 epic, on track AnthonyLaye, raymondtiu AnthonyLaye Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active progress. It has recent updates (4 days ago) and multiple comments showing ongoing testing and development work. Assignees are actively engaged, and the issue is central to the ETv1 -> ETv2 migration effort, which is still in progress. low 2026-03-09 2026-04-10 https://github.com/github/enterprise-primitives/issues/4820
4830 Bosch - An unaffliated user still present in the Enterprise despite the `Remove from the Enterprise` 5: <6mo 36 14 7 support-escalation, support-sev3 robert-crandall ktaggarsi Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev3,' indicating it is a customer-impacting problem that requires attention. It has recent activity, with comments from both the author and assignee within the last 14 days. Additionally, the assignee, robert-crandall, is actively engaged in providing updates and clarifications, suggesting ongoing work. Therefore, this issue is still relevant and actively being worked on. low 2026-03-10 2026-04-01 https://github.com/github/enterprise-primitives/issues/4830
4824 Epic: JOIN splitting: Prepare to move users tables out of mysql1 5: <6mo 36 1 6 epic, on track, mysql1-load-reduction-plan-daily mutle mutle Keep — Active Keep — Active The issue is labeled as 'epic' and 'on track,' indicating active work is being done. It has been updated recently (1 day ago), has ongoing engagement with multiple comments, and an assignee actively working on it. Additionally, the target date has been updated, showing continued progress and attention to the tasks outlined in the issue. low 2026-03-10 2026-04-14 https://github.com/github/enterprise-primitives/issues/4824
4823 `Verify your identity to use Copilot` and `Welcome to your free 30 day trial` messages appear in con 5: <6mo 36 8 3 support-escalation, support-sev2 blkdm0n anna-talley Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring active attention. It was reopened recently, has ongoing engagement with comments from both the author and other contributors, and an assignee is actively involved. Additionally, the issue is only 36 days old and has had updates within the last 8 days, showing it is still relevant and being worked on. low 2026-03-09 2026-04-07 https://github.com/github/enterprise-primitives/issues/4823
4843 User was removed from an organization, but remained as an outside collaborator on one of its reposit 5: <6mo 34 6 10 support-escalation, support-sev2 emisanada bss-mc Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent comments from the assignee discussing ongoing bug fixes and testing. The issue was reopened due to a critical security concern raised by the customer, and there is active engagement from both the assignee and other team members. The 'support-escalation' and 'support-sev2' labels further indicate its priority and relevance. low 2026-03-12 2026-04-08 https://github.com/github/enterprise-primitives/issues/4843
4852 [Feature Request]: Claim a Domain for account management 5: <6mo 33 29 3 Feature Request star6ix9 Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed new feature for domain identity lockdown in GitHub Enterprise. It is not actively being worked on, and recent comments suggest moving the discussion to the customer feedback repository for prioritization and gauging demand. This aligns with the process for handling feature requests, so the issue should be closed and tracked through the feature request process. low 2026-03-13 2026-03-17 https://github.com/github/enterprise-primitives/issues/4852
4900 Investigate indirect_assignments latency for uber-code org (wide team hierarchy) 5: <6mo 30 28 3 eggyhead Keep — Active Needs Discussion The issue involves a complex investigation into latency caused by a specific query path for a large organization with a wide team hierarchy. While some profiling tasks have been completed, there are unresolved questions about optimization strategies, ownership of the issue, and next steps. Recent comments indicate uncertainty about responsibility and potential solutions, suggesting that further discussion is required to clarify the path forward and determine the appropriate team to address the issue. low 2026-03-16 2026-03-18 https://github.com/github/enterprise-primitives/issues/4900
4903 Batch: Update internal enterprise-primitives callsites to avoid future cross-cluster JOINs 5: <6mo 29 1 0 batch mutle, jdennes, AnthonyLaye, tchavas mutle Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent updates (1 day ago) and multiple assignees. It is part of a larger effort linked to another issue (#4824) and has detailed resources and a clear TODO list. The 'batch' label further indicates ongoing work, making it relevant and in-progress. low 2026-03-17 2026-04-14 https://github.com/github/enterprise-primitives/issues/4903
4901 Epic: Move usersd tables out of mysql1 5: <6mo 29 7 2 epic, inactive, mysql1-load-reduction-plan-daily mutle Close — Stale Keep — Backlog The issue is valid and tracks an important initiative to move tables out of the mysql1 cluster, but it is currently on hold pending completion of a preceding epic and dual-write tooling. The 'inactive' label and recent update indicating the dependency suggest it is not actively being worked on but remains relevant and should be kept in the backlog for future prioritization. low 2026-03-17 2026-04-08 https://github.com/github/enterprise-primitives/issues/4901
4910 NoMethodError: undefined method '[]' for nil 5: <6mo 28 28 0 app/sentry Keep — Active Keep — Backlog The issue is relatively recent (28 days old) and appears to be a valid bug report originating from Sentry, indicating a runtime error in the code. However, there has been no activity or engagement since its creation, and no assignees are currently working on it. It should be kept in the backlog for future prioritization. low 2026-03-18 2026-03-18 https://github.com/github/enterprise-primitives/issues/4910
4909 Sev2: Enterprise-level app installation token blocked by org-level IP allow lists on Proxima 5: <6mo 28 27 2 Feature Request, support-escalation, support-sev2, keep jusuchin85 Keep — Active Close → Feature Request The issue has been labeled as 'Feature Request' and a comment from lildude confirms that the behavior described is expected and technically correct, making this a feature request rather than a bug. Additionally, the author has raised a separate customer feedback issue to track this request, indicating that the feature request process is already underway. Therefore, this issue should be closed and tracked through the feature request process. medium 2026-03-18 2026-03-19 https://github.com/github/enterprise-primitives/issues/4909
4907 Department of Premier and Cabinet (Vic) converted org members to outside collaborators and users wer 5: <6mo 28 5 12 support-escalation, support-sev2, done robert-crandall stacycarter Close — Done Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case. It has recent activity, with comments and updates within the last 5 days, and an assignee actively working on it. Additionally, the issue remains open and unresolved, with ongoing discussions and remediation efforts. These signals suggest the issue is actively being worked on and should remain in the 'Keep — Active' bucket. high 2026-03-17 2026-04-10 https://github.com/github/enterprise-primitives/issues/4907
4906 Leverage the newly introduced `business_id` field on `ExternalIdentity` model 5: <6mo 28 28 0 tchavas Keep — Active Keep — Backlog The issue outlines valid optimization opportunities leveraging the `business_id` field on the `ExternalIdentity` model. It is open, has no recent activity, and no assignees, indicating it is not actively being worked on. However, the proposed changes are still relevant and worth keeping for future prioritization. The absence of stale or inactive labels further supports its placement in the backlog. low 2026-03-17 2026-03-17 https://github.com/github/enterprise-primitives/issues/4906
4923 [Feature Request]: SPIKE - Extend EMU username beyond 39-character limit 5: <6mo 27 27 0 Feature Request raymondtiu Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a proposed solution to extend the username character limit for EMU accounts. It is not actively being worked on, has no recent updates or comments, and aligns with the feature request process for tracking customer feedback. Closing it as a feature request ensures it is properly managed within the appropriate workflow. low 2026-03-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4923
4919 Batch: Identify required work for `usersd` service to communicate with the new users DB cluster 5: <6mo 27 1 1 batch mutle Keep — Active Keep — Active The issue is actively being worked on, as evidenced by a recent comment from the author seeking input from collaborators just 1 day ago. It is open, has actionable tasks outlined in the body, and is labeled 'batch,' indicating ongoing relevance to a current initiative. low 2026-03-19 2026-04-14 https://github.com/github/enterprise-primitives/issues/4919
4916 [sev3] `Repository forking` policy description is misleading 5: <6mo 27 27 1 support-escalation, support-sev3, product decision kyanny Keep — Active Needs Discussion The issue has the 'product decision' label, indicating that further discussion or clarification is required to determine the next steps. Additionally, the comment from lildude defers the decision to Product and Design teams, reinforcing the need for further input. The issue is relatively recent (27 days old) and pertains to a support escalation, which suggests it is important but requires a resolution through collaboration and decision-making. low 2026-03-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4916
4912 [Task] Allow org admins to view membership details for Enterprise Teams 5: <6mo 27 27 0 task raymondtiu Keep — Active Keep — Backlog The issue is valid and describes a clear task to enhance functionality for org admins, but it has not been actively worked on or updated in the past 27 days. There are no assignees or recent comments indicating active progress, and the 'task' label suggests it is part of a broader backlog of work. It should be kept for future prioritization. low 2026-03-18 2026-03-18 https://github.com/github/enterprise-primitives/issues/4912
4931 Investigate and create a index on teams that accounts for search by name 5: <6mo 26 26 1 cjs Keep — Active Keep — Backlog The issue is valid and describes a potential improvement to the indexing of the teams table for better search functionality. However, it has not been actively worked on since its creation 26 days ago, and there are no assignees or recent updates indicating active progress. It is worth keeping in the backlog for future prioritization. low 2026-03-20 2026-03-20 https://github.com/github/enterprise-primitives/issues/4931
4928 Intel (P+) - recurring events where team-sync doesn't seem to sync a group as expected 5: <6mo 26 26 2 support-escalation, support-sev2 robert-crandall carlosjnaranjo Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring timely engineering response. The assignee, robert-crandall, has recently commented and taken action to address the problem, suggesting active engagement. Additionally, the issue is only 26 days old and pertains to recurring customer-impacting events, making it relevant and in-progress. low 2026-03-19 2026-03-20 https://github.com/github/enterprise-primitives/issues/4928
4927 Set BusinessTeamOrgAssignments.added_by to non-nil 5: <6mo 26 26 0 robert-crandall Keep — Active Keep — Backlog The issue is valid and describes a clear task related to updating a database column to be non-nillable after certain prerequisites are met. However, there has been no recent activity or engagement since its creation 26 days ago, and it is not marked as actively being worked on. It should remain in the backlog for future prioritization. low 2026-03-19 2026-03-19 https://github.com/github/enterprise-primitives/issues/4927
4938 GHE Server user invited as unaffiliated member cannot access enterprise when GitHub Connect License 5: <6mo 23 14 3 support-escalation, support-sev3 hikanema Keep — Active Needs Discussion The issue is labeled as a 'support-escalation' and 'support-sev3', indicating it requires attention due to customer impact. However, the comments suggest there is ambiguity around the customer's use case and potential dependencies on another issue (#3300). Further discussion is needed to clarify the requirements and determine the appropriate next steps. The issue is relatively recent (23 days old) and has had recent activity (last update 14 days ago), showing it is still relevant and under consideration. low 2026-03-23 2026-04-01 https://github.com/github/enterprise-primitives/issues/4938
4937 Batch: Dashboard for monitoring cross-table JOINs executed in production 5: <6mo 23 13 0 batch mutle mutle Keep — Active Keep — Active The issue is relatively recent (23 days old) and has an assignee actively working on it (mutle). Although there have been no comments, the detailed requirements in the body suggest it is a well-defined and actionable task. The 'batch' label further indicates it is part of ongoing work, and the age and update frequency suggest it is still relevant and in progress. low 2026-03-23 2026-04-02 https://github.com/github/enterprise-primitives/issues/4937
4936 Batch: Move `name` field out of `profiles` into a new `users.display_name` field 5: <6mo 23 0 1 batch, on track jdennes mutle Keep — Active Keep — Active The issue is labeled 'on track,' has recent activity with updates as recent as today, and is actively being worked on by an assignee. The detailed checklist in the issue body indicates ongoing progress, and recent comments show active engagement and decision-making. These signals strongly suggest that the issue is still relevant and actively in progress. low 2026-03-23 2026-04-15 https://github.com/github/enterprise-primitives/issues/4936
4954 Rewrite org soft-deletion to use `users.soft_deleted_at` column 5: <6mo 22 7 1 batch, on track lildude jdennes Keep — Active Keep — Active The issue is labeled 'on track,' indicating active work is ongoing. The assignee, lildude, has provided a recent update (7 days ago) confirming progress and outlining next steps, despite personal delays. The issue is relatively new (22 days old) and still relevant, with dependencies and feature flags actively being managed. These signals suggest the issue is actively being worked on and should remain open. low 2026-03-24 2026-04-08 https://github.com/github/enterprise-primitives/issues/4954
4953 [ADR] Document strategy for moving data to the new cluster 5: <6mo 22 22 0 mtodd Keep — Active Needs Discussion The issue is relatively new (22 days old) and has no comments or updates since its creation. It lacks clear signals of active work or prioritization, and the absence of labels or assignees suggests that further discussion or clarification is needed to determine its next steps. low 2026-03-24 2026-03-24 https://github.com/github/enterprise-primitives/issues/4953
4952 [ADR] Document decision to move tables from mysql1 to a dedicated cluster 5: <6mo 22 22 0 mysql1-load-reduction-plan-daily mtodd Keep — Active Keep — Backlog The issue is relatively recent (22 days old) and has a specific label 'mysql1-load-reduction-plan-daily' indicating it is part of a broader plan. However, there has been no activity or updates since its creation, and no assignees are currently working on it. This suggests it is valid but not actively being worked on, making it suitable for the backlog. low 2026-03-24 2026-03-24 https://github.com/github/enterprise-primitives/issues/4952
4951 Bug: Proxima trials is not passing `country` value to `form>table` 5: <6mo 22 5 8 bug, priority-2 raymondtiu Keep — Active Keep — Active The issue is actively being discussed and has recent engagement, including comments from multiple contributors within the last 5 days. It is marked as a 'bug' with 'priority-2,' indicating it is important and being tracked on the First Responder board for resolution. Additionally, specific next steps have been identified, and the issue is in progress. low 2026-03-24 2026-04-10 https://github.com/github/enterprise-primitives/issues/4951
4950 Bug: DFD Trial Seat Usage 5: <6mo 22 15 8 bug AnthonyLaye erikaxu Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent comments from the assignee, AnthonyLaye, who has opened a PR to address the bug. The issue is only 22 days old, has had meaningful engagement with 8 comments, and the assignee is actively discussing and implementing solutions. These signals indicate that the issue is still relevant and in-progress. low 2026-03-24 2026-03-31 https://github.com/github/enterprise-primitives/issues/4950
4949 Batch: Domain Isolation for BusinessUserAccounts 5: <6mo 22 22 0 batch robert-crandall robert-crandall Keep — Active Keep — Active The issue is relatively new (22 days old), has an assignee (robert-crandall), and outlines a detailed plan for implementing domain isolation for the `BusinessUserAccount` model. While there are no comments or updates since creation, the presence of an assignee and the comprehensive scope of work suggest that this issue is actively being worked on or is in the early stages of progress. The 'batch' label further supports its relevance to ongoing batch-related work. low 2026-03-23 2026-03-23 https://github.com/github/enterprise-primitives/issues/4949
4968 Backfill and sync soft deleted date from `soft_deleted_organizations` to `users.soft_deleted_at` 5: <6mo 21 21 0 on track lildude lildude Keep — Active Keep — Active The issue is labeled as 'on track,' indicating active progress or prioritization. It is relatively recent, being only 21 days old, and has an assignee actively associated with it. While there are no comments or updates since its creation, the 'on track' label and the dependency on a related migration suggest that it is still relevant and being worked on. low 2026-03-25 2026-03-25 https://github.com/github/enterprise-primitives/issues/4968
4978 Batch: Domain isolation: Business (`packages/admin`) 5: <6mo 20 20 0 batch mutle mutle Keep — Active Keep — Active The issue is actively assigned to a contributor (mutle) and was created and last updated only 20 days ago, indicating recent engagement. It has detailed information about the current state and goals, suggesting that work is ongoing or planned. The 'batch' label further supports that this is part of an active effort or initiative. Therefore, it should remain in the active bucket. low 2026-03-26 2026-03-26 https://github.com/github/enterprise-primitives/issues/4978
4976 Epic: Domain Isolation: Prepare to move users tables out of mysql 5: <6mo 20 20 0 epic mutle Keep — Active Keep — Backlog The issue is labeled as 'epic,' indicating it is part of a larger initiative. It is relatively recent (20 days old) and has no comments or updates since creation, suggesting it is not actively being worked on at the moment. However, the tasks outlined in the body are clear and valid, making it worth keeping in the backlog for future prioritization. low 2026-03-26 2026-03-26 https://github.com/github/enterprise-primitives/issues/4976
4972 Bug: Cannot convert member without 2FA to outside collaborator, 2FA required for outside collaborato 5: <6mo 20 20 1 bug app/sentry Keep — Active Keep — Active The issue is labeled as a 'bug', is open, and was created only 20 days ago with recent engagement from a commenter referencing related activity. This indicates the issue is still relevant and may be actively worked on or monitored. low 2026-03-26 2026-03-26 https://github.com/github/enterprise-primitives/issues/4972
5072 Removing organization member via API did not remove team membership 5: <6mo 20 1 8 support-escalation, support-sev2, non-scaling-related iamhubber Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority customer-facing issue. It has recent activity, including comments from both the author and other contributors within the last day. The issue is still open and actively being investigated, as evidenced by the ongoing discussion and log queries. These signals suggest the issue is actively being worked on and remains relevant. low 2026-03-26 2026-04-14 https://github.com/github/enterprise-primitives/issues/5072
4992 [github/orgs] Accessibility Violations Tracking Issue 🧰 5: <6mo 19 19 0 app/accessibility-bot-app Keep — Active Keep — Active The issue is actively tracking accessibility violations identified by automated scans, which are important for maintaining inclusivity and reducing legal risks. Although there has been no recent activity or comments, the issue is maintained by a bot and will automatically update based on new scans or resolved violations. This indicates that the issue is still relevant and in-progress. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4992
4990 Batch: Domain Isolation: EnterpriseTeam, EnterpriseTeamMembership & EnterpriseTeamGroupMapping Write 5: <6mo 19 19 0 batch mutle Keep — Active Keep — Backlog The issue is valid and tracks important work to create a domain interface for write operations in the `EnterpriseTeams` package. It has been open for only 19 days, with no recent updates or active engagement, and no assignees. The 'batch' label suggests it is part of a larger effort but not actively being worked on at the moment. Therefore, it should remain in the backlog for future prioritization. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4990
4989 Batch: Domain Isolation: BusinessTeamOrgAssignment Model Write Operations 5: <6mo 19 16 0 batch mutle mutle Keep — Active Keep — Active The issue is relatively recent (19 days old) and has an assignee actively working on it, indicating ongoing progress. The detailed scope and technical breakdown suggest that this is a well-defined and relevant task. Although there has been no recent comment activity, the presence of an assignee and the specificity of the issue imply it is actively being worked on. low 2026-03-27 2026-03-30 https://github.com/github/enterprise-primitives/issues/4989
4988 Domain Isolation: Write operations for remaining models 5: <6mo 19 19 0 mutle Keep — Active Keep — Backlog The issue is relatively new (19 days old) and outlines dependencies on other issues, indicating it is part of a larger effort. However, there has been no recent activity or engagement, and no assignees are currently working on it. The lack of updates suggests it is not actively being worked on but remains valid and worth keeping for future prioritization. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4988
4987 Batch: Domain Isolation: Integration Model Write Operations 5: <6mo 19 19 1 batch mutle Keep — Active Needs Discussion The issue outlines a significant architectural change involving domain isolation for write operations on the `Integration` model, which appears to be a blocker due to unfamiliarity with the `github/apps` package and its implications. The recent comment from the author highlights the need for further clarification and discussion, particularly around the scope and impact of the proposed changes. No active work or resolution is evident, and the issue requires input from relevant stakeholders before proceeding. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4987
4986 Batch: Domain Isolation: Team Model Write Operations 5: <6mo 19 16 0 batch mutle Keep — Active Keep — Backlog The issue is valid and tracks important work related to exposing write operations through the domain interface for the `teams` table. It has been open for 19 days with no recent updates or active engagement, and no assignees are currently working on it. The presence of the 'batch' label suggests it is part of a larger batch of work, but it is not actively being worked on at the moment. Therefore, it is appropriate to keep this issue in the backlog for future prioritization. low 2026-03-27 2026-03-30 https://github.com/github/enterprise-primitives/issues/4986
4985 Batch: Domain Isolation: BusinessMemberInvitation Model Write Operations 5: <6mo 19 19 1 batch mutle Keep — Active Keep — Backlog The issue is valid and outlines a clear scope for addressing write operations on the `BusinessMemberInvitation` model. However, the recent comment from the author indicates that this work has been deprioritized and is not actively being worked on. The issue is still relevant and worth keeping for future consideration, but it does not require immediate action. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4985
4984 Batch: Domain Isolation: BusinessOrganizationInvitation Model Write Operations 5: <6mo 19 19 1 batch mutle Keep — Active Keep — Backlog The issue is valid and tracks important work to enforce privacy and proper domain isolation for the `BusinessOrganizationInvitation` model. Although the author mentioned deprioritizing it due to unrelated migrations, the issue remains open and has a 'batch' label, indicating it is part of a larger effort. There has been no recent activity, but the issue is still relevant and worth keeping for future prioritization. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4984
4983 Batch: Domain Isolation: Organization Model Write Operations 5: <6mo 19 19 0 batch mutle Keep — Active Keep — Backlog The issue is valid and outlines a clear scope of work for exposing write operations through `Orgs::Domain`. It has been open for 19 days with no recent updates or activity, but it is not marked as stale or inactive. The detailed proposal and sub-issues suggest it is worth keeping in the backlog for future prioritization. low 2026-03-27 2026-03-27 https://github.com/github/enterprise-primitives/issues/4983
4982 Batch: Domain Isolation: User Model Write Operations 5: <6mo 19 1 0 batch mutle Keep — Active Keep — Active The issue is actively being worked on, as evidenced by its recent update (1 day ago) and detailed scope and proposed implementation plan. It is labeled 'batch,' indicating it is part of a larger effort, and the issue is still open with no signs of inactivity or irrelevance. The structured breakdown of sub-issues and proposed domain interfaces further suggests ongoing engagement and relevance. low 2026-03-27 2026-04-13 https://github.com/github/enterprise-primitives/issues/4982
4981 Epic: Update terms of service type for free organization creation flow 5: <6mo 19 19 0 epic raymondtiu Keep — Active Keep — Backlog The issue is labeled as 'epic' and outlines a clear scope of work related to updating terms of service for free organization creation flow. While it has not been actively updated in the past 19 days and has no assignees or comments, the described tasks and impact indicate that it is still valid and worth keeping for future prioritization. There are no signals suggesting it is stale or resolved, and it does not require immediate discussion. low 2026-03-26 2026-03-26 https://github.com/github/enterprise-primitives/issues/4981
4997 [github/move_work] [dotcom] [move_work_move_work#show] [HPC] Web Performance Scorecard Issue 5: <6mo 18 1 0 app/web-systems-bot Keep — Active Keep — Active The issue is actively maintained by automated systems, as indicated by the note in the body stating that robots manage its lifecycle. It was updated just 1 day ago, and the findings are still relevant with a due date in the future (2026-05-09). There is no indication that the issue is stale or resolved, and it is tied to ongoing performance monitoring efforts. low 2026-03-28 2026-04-14 https://github.com/github/enterprise-primitives/issues/4997
4999 Instrument audit log events when email verification for enterprise trials occur 5: <6mo 17 17 0 support-escalation, support-sev3 joshuawalker Keep — Active Keep — Active The issue is labeled as a 'support-escalation' with a severity level of 'sev3,' which indicates that engineering must respond within one week. Although there has been no activity since its creation 17 days ago, the issue is still open and pertains to a customer-facing problem that requires instrumentation for audit log events. Its relevance and urgency suggest it is actively being tracked and should remain in the active bucket for resolution. low 2026-03-28 2026-03-28 https://github.com/github/enterprise-primitives/issues/4999
5011 Domain Isolation for BusinessUserAccount: Enable privacy enforcement and final violation burndown 5: <6mo 16 16 0 robert-crandall Keep — Active Needs Discussion The issue lacks labels, comments, and assignee activity, and the body does not provide sufficient detail to determine its current relevance or priority. Further discussion is needed to clarify the scope and importance of the issue before deciding its next steps. low 2026-03-30 2026-03-30 https://github.com/github/enterprise-primitives/issues/5011
5004 [github/orgs] Accessibility Violations Tracking Issue 🧰 5: <6mo 16 16 0 app/accessibility-bot-app Keep — Active Keep — Active The issue is actively tracking accessibility violations identified by automated scans, which are important for maintaining inclusivity and reducing legal risks. It was created recently (16 days ago) and is maintained by a bot that ensures ongoing relevance. The issue is open and has clear instructions for resolution, indicating it is still relevant and in-progress. low 2026-03-30 2026-03-30 https://github.com/github/enterprise-primitives/issues/5004
5002 ActiveRecord::RecordNotUnique: `Duplicate entry '3750997-ua_zicd_10_per_service_operators' for key ' 5: <6mo 16 2 3 app/sentry Keep — Active Keep — Active The issue is actively being discussed and investigated, with recent comments and updates within the last 2 days. It appears to be related to a critical error causing incidents, as referenced in linked Slack and PagerDuty discussions. The issue is still open and relevant, with ongoing engagement from team members. low 2026-03-30 2026-04-13 https://github.com/github/enterprise-primitives/issues/5002
5017 GHES 3.21 QA Signoff for: MEAO 5: <6mo 15 15 0 3-21-QA-signoff wallace, emisanada faizatakhan Keep — Active Keep — Active The issue is labeled '3-21-QA-signoff,' indicating it is part of the QA process for GHES 3.21, which has a clear deadline of April 14, 2026. It is actively assigned to multiple individuals, including wallace and emisanada, and has been updated recently (15 days ago). The issue outlines specific required actions and accountability roles, suggesting it is still relevant and in-progress. No comments or inactivity signals suggest it is being actively worked on. low 2026-03-31 2026-03-31 https://github.com/github/enterprise-primitives/issues/5017
5016 GHES 3.21 QA Signoff for: Identity Teams 5: <6mo 15 15 0 3-21-QA-signoff eggyhead faizatakhan Keep — Active Keep — Active The issue is labeled '3-21-QA-signoff,' indicating it is part of an active QA process for GHES 3.21. It has an assignee, a clear deadline (April 14, 2026), and specific required actions outlined in the body. Although there are no comments or recent updates, the issue is only 15 days old and still within the timeline for QA sign-off, suggesting it is actively relevant and in-progress. low 2026-03-31 2026-03-31 https://github.com/github/enterprise-primitives/issues/5016
5015 Drop `soft_deleted_organizations` 5: <6mo 15 15 0 lildude lildude Keep — Active Keep — Active The issue is relatively new (15 days old) and has an assignee actively assigned to it, indicating it is being worked on. Additionally, it references a related issue (#5014) that appears to be part of an ongoing effort. There is no indication that the issue is stale or resolved, so it should remain active. low 2026-03-31 2026-03-31 https://github.com/github/enterprise-primitives/issues/5015
5014 Stop writing to `soft_deleted_organizations` when soft-deleting org 5: <6mo 15 15 0 lildude lildude Keep — Active Keep — Active The issue is relatively new (15 days old), has an assignee (lildude), and references dependencies that are actively being worked on. These signals indicate that the issue is still relevant and in-progress, warranting placement in the 'Keep — Active' bucket. low 2026-03-31 2026-03-31 https://github.com/github/enterprise-primitives/issues/5014
5036 Reinstate collaborator questions 5: <6mo 14 5 4 support-escalation, support-sev3 wi11ialvl Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev3,' indicating it is part of an active support process with a one-week response expectation. The issue has recent engagement, with comments exchanged within the last 5 days, and the author is actively testing and reporting back. These signals suggest the issue is still relevant and being worked on. low 2026-04-01 2026-04-10 https://github.com/github/enterprise-primitives/issues/5036
5043 Task: break joins for `business_member_invitations` 5: <6mo 13 7 0 task AnthonyLaye mutle Keep — Active Keep — Active The issue is open, has an assignee (AnthonyLaye), and was updated recently (7 days ago). It is marked as a 'task' and references a dependency on another issue, indicating active work or planning. There are no signs of inactivity or irrelevance, and the detailed query analysis suggests ongoing technical engagement. low 2026-04-02 2026-04-08 https://github.com/github/enterprise-primitives/issues/5043
5041 Bug: Unable to invite user 5: <6mo 13 13 5 bug, good first issue stephanmiehe Keep — Active Keep — Active The issue is actively being discussed and was recently reopened to address related concerns about expired trials leading to 404 errors. Comments from multiple contributors suggest ongoing engagement and a potential solution involving button visibility changes. The 'bug' label and recent activity indicate that the issue is still relevant and being worked on. low 2026-04-01 2026-04-02 https://github.com/github/enterprise-primitives/issues/5041
5062 Owner removed from transferred organization on Enterprise trial cancellation 5: <6mo 10 1 5 support-escalation, support-sev2, non-scaling-related blkdm0n anna-talley Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring prompt attention. The issue is open, has recent activity (last updated 1 day ago), and has active engagement from multiple participants, including assignees and commenters discussing potential fixes and next steps. Additionally, the issue involves a customer-impacting problem that has not yet been fully resolved, as evidenced by the ongoing discussion about the root cause and resolution. These signals suggest the issue is actively being worked on and should remain in the 'Keep — Active' bucket. low 2026-04-05 2026-04-14 https://github.com/github/enterprise-primitives/issues/5062
5066 Disable Self-serve CB/CE and Copilot trials due to Incident 4199 5: <6mo 9 1 3 AnthonyLaye AnthonyLaye Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent updates (last updated 1 day ago), active engagement in comments, and assigned ownership by AnthonyLaye. The issue involves ongoing work to address a critical incident and implement feature flags to mitigate abuse of enterprise trial accounts. Additionally, there are detailed plans and progress updates provided, indicating that the issue is still relevant and in-progress. low 2026-04-06 2026-04-14 https://github.com/github/enterprise-primitives/issues/5066
5084 [Feature Request]: a setting to hide enterprise admins from organization people views 5: <6mo 7 7 2 Feature Request, non-scaling-related jeffwilcox Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a potential enhancement to hide enterprise admins from organization views. While the problem and proposed solution are well-articulated, there is no indication of active work or prioritization, as confirmed by the comment from @erikaxu stating that the team is focused on other priorities for the short term. Closing this issue as a feature request ensures it can be tracked through the appropriate process for future consideration. low 2026-04-08 2026-04-08 https://github.com/github/enterprise-primitives/issues/5084
5082 Proxima/GHE enterprises showing deleted organizations in org list 5: <6mo 7 4 10 support-escalation, support-sev2 lildude adamrr724 Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support issue requiring active attention. The assignee, lildude, has been actively engaging with the issue, providing updates and confirming fixes. Recent comments within the last few days show ongoing discussion and resolution attempts. Given the severity and recent activity, this issue is clearly still relevant and actively being worked on. low 2026-04-08 2026-04-11 https://github.com/github/enterprise-primitives/issues/5082
5081 [github/enterprise_accounts] [prod-sdc-01] [businesses_admins#index] [CLS] Web Performance Scorecard 5: <6mo 7 1 0 app/web-systems-bot Keep — Active Keep — Active The issue is actively maintained by an automated system and has been updated recently (1 day ago). It is tied to ongoing web performance remediation efforts for the 'github/enterprise_accounts' service, with a clear due date for action items (2026-05-20). The automated nature of the issue ensures it remains relevant and up-to-date, and the lack of manual closure instructions indicates it should remain open for tracking purposes. low 2026-04-08 2026-04-14 https://github.com/github/enterprise-primitives/issues/5081
5089 Epic: Address impact of EMU-suspended users on enterprise user limits 5: <6mo 6 6 0 epic wallace, jdennes, erikaxu erikaxu Keep — Active Keep — Active The issue is labeled as an 'epic,' indicating it is a high-level tracking issue for a significant initiative. It was created and last updated only 6 days ago, showing recent engagement. Additionally, it has active assignees (wallace, jdennes, erikaxu), and the tasks outlined suggest ongoing work. These signals indicate that the issue is actively being worked on and is still relevant. low 2026-04-09 2026-04-09 https://github.com/github/enterprise-primitives/issues/5089
5088 Task: break `JOIN`s for the `primary_avatars` table 5: <6mo 6 6 0 task tchavas tchavas Keep — Active Keep — Active The issue is labeled as 'task,' has an active assignee (tchavas), and was created and last updated only 6 days ago. There has been no recent activity or comments, but the issue is still fresh and appears to be actively assigned for work. Therefore, it should remain in the 'Keep — Active' bucket. low 2026-04-09 2026-04-09 https://github.com/github/enterprise-primitives/issues/5088
5087 Salesforce - DR API org/repo calls return 403 via `api.` subdomain 5: <6mo 6 1 1 support-escalation, support-sev2, non-scaling-related blkdm0n MystaMax Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring timely resolution. The assignee, blkdm0n, has recently commented with investigative findings, showing active engagement. Additionally, the issue is only 6 days old and was updated just 1 day ago, further confirming its relevance and ongoing work. low 2026-04-08 2026-04-14 https://github.com/github/enterprise-primitives/issues/5087
5086 Bug: Customer can bypass Enterprise Team member limit through IDP sync 5: <6mo 6 1 3 bug, non-scaling-related blkdm0n AnthonyLaye Keep — Active Keep — Active The issue is actively being worked on, as evidenced by recent comments and engagement from multiple contributors, including the assignee blkdm0n, who is investigating the problem and seeking feedback. The issue is only 6 days old, has recent updates, and addresses a critical bug related to enterprise team member limits, which is still relevant and requires resolution. These signals indicate that the issue is actively being worked on and should remain open. low 2026-04-08 2026-04-14 https://github.com/github/enterprise-primitives/issues/5086
5095 Task: break `JOIN`s for `enterprise_team_assignments` table 5: <6mo 5 4 0 task tchavas tchavas Keep — Active Keep — Active The issue is labeled as 'task', has been recently created (5 days old), and has an active assignee (tchavas). These signals indicate that the issue is actively being worked on or is in progress, making it relevant to keep in the active bucket. low 2026-04-10 2026-04-10 https://github.com/github/enterprise-primitives/issues/5095
5092 [Feature Request]: Button to Return Enterprise to Trial Flow 5: <6mo 5 0 2 Feature Request, backlog, non-scaling-related ItsJustJefu Keep — Active Close → Feature Request The issue is labeled as 'Feature Request' and describes a new functionality to add a button for returning Enterprise instances to the trial flow. While the issue is valid and has recent activity, it is not actively being worked on and fits the criteria for tracking through the feature request process. The comments also suggest that the impact is being monitored and alternative solutions are being considered, indicating that this is not yet a priority for active development. low 2026-04-10 2026-04-15 https://github.com/github/enterprise-primitives/issues/5092
5091 Task: break `JOIN`s for `team_membership_requests` table 5: <6mo 5 1 1 done, task tchavas tchavas Close — Done Close — Done The issue is labeled as 'done,' marked as 'CLOSED (COMPLETED),' and has recent activity confirming the work has been completed. Although there was a comment about reopening due to a reverted PR, the issue remains closed and the work appears to have been finalized. Therefore, it should be categorized as 'Close — Done.' high 2026-04-10 2026-04-13 https://github.com/github/enterprise-primitives/issues/5091
5097 `Basic` to `Full` migration confirmation email looks strange in Outlook 5: <6mo 4 4 0 raymondtiu Keep — Active Needs Discussion The issue describes a formatting problem with a confirmation email in Outlook, but lacks sufficient detail or context to determine the next steps. There are no labels, assignees, or comments to indicate active work or prioritization, and the issue is only 4 days old. Further discussion is needed to clarify the scope of the problem and decide on a resolution path. low 2026-04-10 2026-04-10 https://github.com/github/enterprise-primitives/issues/5097
5096 Force Copilot seat assignment to the new v2 enterprise teams after the migration 5: <6mo 4 2 3 AnthonyLaye raymondtiu Keep — Active Close — Done The issue is marked as 'done', the state is 'closed (completed)', and the resolution is confirmed in the comments with a linked pull request. Recent activity indicates the work has been completed successfully, and there is no further action required. low 2026-04-10 2026-04-13 https://github.com/github/enterprise-primitives/issues/5096
5100 Bug: RestoreOrganizationUserJob causes a low rate of deadlocks on Abilities 5: <6mo 2 1 0 bug, non-scaling-related cjs Keep — Active Keep — Active The issue is only 2 days old, has a detailed description of the bug, and references potential solutions and related PRs. It is labeled as 'bug' and is clearly relevant to ongoing work, with recent updates indicating active engagement. No comments or assignees yet, but the issue is fresh and actionable. low 2026-04-13 2026-04-14 https://github.com/github/enterprise-primitives/issues/5100
5112 Task: Ensure no joins for `organization_membership_entries` 5: <6mo 1 0 0 task AnthonyLaye mutle Keep — Active Keep — Active The issue is newly created (1 day old), has an assignee actively working on it, and is labeled as a 'task'. Additionally, it has been recently updated, indicating active engagement. These signals suggest the issue is currently being worked on and should remain active. low 2026-04-14 2026-04-15 https://github.com/github/enterprise-primitives/issues/5112
5104 Task: break joins for member_feature_requests 5: <6mo 1 0 1 task robert-crandall AnthonyLaye Keep — Active Keep — Active The issue is actively being worked on, as evidenced by its recent creation (1 day old), recent update (0 days ago), and engagement through comments. Additionally, it has an assignee (robert-crandall), indicating active ownership. The 'task' label further suggests that this is an actionable item currently in progress. low 2026-04-13 2026-04-15 https://github.com/github/enterprise-primitives/issues/5104
5101 Task: break joins for enterprise_teams 5: <6mo 1 1 0 task mutle AnthonyLaye Keep — Active Keep — Active The issue is newly created (1 day old), has an assignee (mutle), and is labeled as a 'task,' indicating active work is likely underway. There is no indication of inactivity or irrelevance, and the issue appears to be in progress based on its recent creation and update dates. low 2026-04-13 2026-04-14 https://github.com/github/enterprise-primitives/issues/5101
5116 Managed users always encounter 500 error during accessing to Gists when user-level enforcement IP al 5: <6mo 0 0 1 support-escalation, support-sev2, non-scaling-related catto Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring prompt attention. It was created and updated today, showing active engagement. Additionally, the issue is tied to a specific customer impact and includes relevant context and links, such as a Zendesk ticket and Splunk logs. The recent comment suggests ongoing investigation or relevance to an upcoming feature release. These signals collectively justify keeping the issue active for immediate resolution. low 2026-04-15 2026-04-15 https://github.com/github/enterprise-primitives/issues/5116
5115 Account `admin-mm_WAM` repeatedly demoted from owner to member in `weiss-internal` organization 5: <6mo 0 0 0 support-escalation, support-sev2, non-scaling-related bss-mc Keep — Active Keep — Active The issue is labeled as 'support-escalation' and 'support-sev2,' indicating it is a high-priority support case requiring engineering response within one business day. It was created and updated today, showing active engagement. The detailed context and severity classification further confirm its relevance and urgency, making it appropriate to keep this issue active for immediate attention. low 2026-04-15 2026-04-15 https://github.com/github/enterprise-primitives/issues/5115
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment