Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project boards / kanban: Support for organization-level boards #13405

Closed
mappu opened this issue Nov 2, 2020 · 5 comments · Fixed by #22235
Closed

Project boards / kanban: Support for organization-level boards #13405

mappu opened this issue Nov 2, 2020 · 5 comments · Fixed by #22235
Labels
topic/projects type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@mappu
Copy link
Contributor

mappu commented Nov 2, 2020

  • Gitea version (or commit ref): 1.13.0-rc1

Description

Hi, the new Project feature is wonderful, a huge thanks to everyone who helped develop it.

As part of the big #8346 PR there was some support for organization boards and user boards (if a project is OrganizationType), but it's not exposed in the UI as far as I can tell (e.g. see also #11293 (comment) ).

I think the most recent status is from this comment: #8346 (review)

  • cleanup some left over for ProjectTypeIndividual and ProjectTypeOrganization
    • or finish to implement the ui

I still would prefer to remove (or at least comment) the code related to User and Org project since it is not fully implemented before merging but I would not be against merging this PR like this since it would help to have other work on this.


This issue is a feature request to track exposing organization board support in the UI,

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Nov 3, 2020
@lunny lunny mentioned this issue Feb 17, 2021
15 tasks
@senderic
Copy link

I would also benefit for an issue board that is at the Organization level. This will allow issues to be reference by multiple sub-repositories within the organization.

@6543 6543 self-assigned this Jul 2, 2022
@6543 6543 added this to the 1.18.0 milestone Jul 2, 2022
@genofire
Copy link

One reason, why i still prefer gitlab (beside the good ci integration)

@zander
Copy link

zander commented Jul 25, 2022

A handy usecase written out on a seperate issue (#20203) copied here may be useful;

Imagine the usecase of an organization that uses a shared library git repo as well as a couple of application repositories which all get released at the same time.
Repos are grouped by who develops in them, afterall.

A new feature could be a "project" and that might touch multiple repositories in such an organization and while issues can have dependencies this doesn't solve the issue of having a nice overview of all the issues across all the repositories.

Similarly, a milestone could be used to identify all the remaining issues for "the next release", which covers multiple repositories. It would be very useful to list all the issues assigned to this milestone in an organization and not having to go to each repo where this is duplicated.

@6543
Copy link
Member

6543 commented Jul 25, 2022

projects are structured in backend already ... just need some work in go code and frontend templates ...

@6543 6543 modified the milestones: 1.18.0, 1.19.0 Oct 16, 2022
@6543 6543 removed their assignment Dec 29, 2022
@6543
Copy link
Member

6543 commented Dec 29, 2022

lunny did got it first :D #22235

lunny added a commit that referenced this issue Jan 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/projects type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants