Adding issues, wiki page to the organisation #3685

New Issue

GiteaMirror · 2025-11-02T05:21:42-06:00

GiteaMirror commented

2025-11-02 05:21:42 -06:00

Originally created by @iddm on GitHub (Jul 27, 2019).

This is a feature request.

I think it would be nice to have an issue page as same as repositories have, but for the whole organization. Now I need to split one product issue between several repositories because the feature must be partially developed in many of repositories, not only one. This is not really convenient and useful. Also, it would be nice if an organization had milestones as well. Or just the same issues page as repositories do.

I propose either to create a "product" type of thing which has all of that or add all of this to the "organization" type.

Originally created by @iddm on GitHub (Jul 27, 2019). This is a feature request. I think it would be nice to have an issue page as same as repositories have, but for the whole organization. Now I need to split one product issue between several repositories because the feature must be partially developed in many of repositories, not only one. This is not really convenient and useful. Also, it would be nice if an organization had milestones as well. Or just the same issues page as repositories do. I propose either to create a "product" type of thing which has all of that or add all of this to the "organization" type.

GiteaMirror added the type/proposal label 2025-11-02 05:21:42 -06:00

GiteaMirror commented

2025-11-02 05:21:43 -06:00

@nodiscc commented on GitHub (Apr 19, 2020):

the feature must be partially developed in many of repositories, not only one.

Same situation here, another solution would be to keep issues at the repository level, but add a dashboard to organizations, that shows all issues for repositories inside the organization (this is what Gitlab does).

Organization-level milestones would be really nice though.

@nodiscc commented on GitHub (Apr 19, 2020): > the feature must be partially developed in many of repositories, not only one. Same situation here, another solution would be to keep issues at the repository level, but add a dashboard to organizations, that shows all issues for repositories inside the organization (this is what Gitlab does). Organization-level milestones would be _really_ nice though.

GiteaMirror commented

2025-11-02 05:21:43 -06:00

@deptyped commented on GitHub (Aug 23, 2020):

It would also be nice to have projects for the whole organization

@deptyped commented on GitHub (Aug 23, 2020): It would also be nice to have projects for the whole organization

GiteaMirror referenced this issue

2025-11-02 12:24:56 -06:00

[PR #3685] [CLOSED] Switch syntax highlighting to PrismJS #17042

Sign in to join this conversation.