Organization-wide issues #10566

New Issue

GiteaMirror · 2025-11-02T09:11:26-06:00

GiteaMirror commented

2025-11-02 09:11:26 -06:00

Originally created by @JOKUE2002 on GitHub (Mar 30, 2023).

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

Originally created by @JOKUE2002 on GitHub (Mar 30, 2023). ### 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_

GiteaMirror added the type/proposal issue/workaround labels 2025-11-02 09:11:26 -06:00

GiteaMirror commented

2025-11-02 09:11:27 -06:00

@silverwind commented on GitHub (Mar 31, 2023):

Yes, this is needed. I could also see additionally:

Per-User issues. So people can post their TODOs, ask question to users etc. Like https://github.com/sindresorhus/meta
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.

@silverwind commented on GitHub (Mar 31, 2023): Yes, this is needed. I could also see additionally: - Per-User issues. So people can post their TODOs, ask question to users etc. Like https://github.com/sindresorhus/meta - 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.

GiteaMirror commented

2025-11-02 09:11:27 -06:00

@coldhearti commented on GitHub (Jan 23, 2025):

This is definitely needed! A very useful feature for organisations that use GITea project management features for more than just code.

@coldhearti commented on GitHub (Jan 23, 2025): This is definitely needed! A very useful feature for organisations that use GITea project management features for more than just code.

GiteaMirror commented

2025-11-02 09:11:27 -06:00

@wxiaoguang commented on GitHub (Jan 24, 2025):

I used to do this:

/owner/dev-issues
/owner/dev-frontend
/owner/dev-backend

And disable the "issues" unit in the dev-frontend and dev-backend, disable the "code" unit in dev-issues, only use dev-issues to manage the issues and milestones.

To be honest, changing the current "issues" module is quite difficult, I think the dedicate dev-issues repo should satisfy the requirement here?

@wxiaoguang commented on GitHub (Jan 24, 2025): I used to do this: ``` /owner/dev-issues /owner/dev-frontend /owner/dev-backend ``` And disable the "issues" unit in the `dev-frontend` and `dev-backend`, disable the "code" unit in `dev-issues`, only use `dev-issues` to manage the issues and milestones. To be honest, changing the current "issues" module is quite difficult, I think the dedicate `dev-issues` repo should satisfy the requirement here?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10566