Projects v2 always defaulting to LPEUnity repository when creating issues

[LiviaCristinaT]

Select Topic Area

Question

Feature Area

Projects

Body

Description

We are experiencing unexpected behavior in GitHub Projects (v2) at the organization level.

When creating a new issue from any project board, the issue creation modal always defaults to the repository LPEUnity, even when:

The project default repository is configured as another repository (e.g., Geosol)

• The project view clearly shows items from different repositories

• The user has admin permissions

• The behavior is tested in an incognito window

• No recent configuration changes were made

This has been happening for several months.

Expected behavior

New issues created from a project should default to the repository configured in the project's "Default repository" setting.

Actual behavior

The issue creation modal always defaults to LPEUnity, regardless of the project configuration.

Could you clarify whether:

This is intended behavior?

A known issue?

Or a configuration conflict at organization level?

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[yraj-17]

Hey, just to add to what’s already been mentioned — I’ve run into similar behavior in GitHub Projects as well, and it does seem tied to how the issue creation modal handles context internally.

One thing I noticed is that the modal often “remembers” the last active or most frequently used repository in the session, even if the project has a different default repository configured. So sometimes it’s not just the oldest repo — it can also feel like a state/caching issue depending on usage.

A couple of small things that might be worth trying (not fixes, but can help confirm behavior):

Try creating an issue right after switching context to another repo (before opening the project)
Check if the selected repo changes after manually selecting a different one once
Test with a different user account in the same org to rule out session-specific behavior

Also, if your project pulls items from multiple repositories, the modal might not always prioritize the project’s default setting consistently, which makes the experience a bit unpredictable.

So yeah — definitely doesn’t look like a configuration issue on your side. More like a mix of UI state + known limitation/bug.

Curious if others have seen the same “last used repo” behavior too.