You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scope of an issue is currently only repository-wide. A support for organization-wide issues would be useful for managing and triaging issues that apply to multiple projects in a wider scope (in this case the organization).
For example an issue might apply to the frontend and backend repository in an organization.
Or if you want to manage the business end of things through a gitea one would be able to do it in a higher level instead of creating an empty repository for it.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
JOKUE2002
added
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
type/proposal
The new feature has not been accepted yet but needs to be discussed first.
labels
Mar 30, 2023
lunny
removed
the
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
label
Mar 31, 2023
Server-wide issues. Sometimes with an issue affecting multiple organizations or when you as an admin want to broadcast some info to all users, I see a benefit of having this level above as well.
Feature Description
This feature request is quite similar to #20203 .
The scope of an issue is currently only repository-wide. A support for organization-wide issues would be useful for managing and triaging issues that apply to multiple projects in a wider scope (in this case the organization).
For example an issue might apply to the frontend and backend repository in an organization.
Or if you want to manage the business end of things through a gitea one would be able to do it in a higher level instead of creating an empty repository for it.
Screenshots
No response
The text was updated successfully, but these errors were encountered: