Creating an issue from a Project, when the Project has a default repo #170410
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Feature Area
Projects
Body
We are on Github Enterprise and are migrating our project management flow over to Github Projects & Issues.
I think we've discovered a bug. When a Project has a default repo set, it seems to conflict with when trying to create an Issue that's not in that default repo.
With Project-level default repo set:
#To refer to a repo -> select a repoThis behavior does not happen when no default repo is selected. Please see attached screenshots.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions