# Basic concept of Organisation, Repository, Milestone, Project

**URL:** <https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719>\
**Category:** General\
**Created:** [August 18, 2022, 11:45am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719 "2022-08-18T11:45:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrall](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@mrall](https://forum.gitea.com/u/mrall)\
**Post date:** [August 18, 2022, 11:45am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/1 "2022-08-18T11:45:02Z")

</div>

Hi,

I’m trying to figure out the structural components of gitea - namely Organization, Repository, Milestone and Project.

Coming from a gitlab background it’s not 100% clear to me, how to organize these. Especially Organization and Project are new to me.

I didn’t find any documentation like “how to organize your projects with gitea”.

In my case I have different customers, with different projects, each project containing multiple repositories (like src, doc, bin, etc.). So customers would fit into “organizations”. In gitlab I had sub-projects to represent the customers projects and under these there were the repos. It would be not a problem to put all repos under the organization - I just want to be sure to understand the concept.

Maybe somebody can explain the concepts or give some examples what to put where.

cheers

---

<div class="post-metadata">

**Author:** ![cbrake](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/cbrake/32/4809_2.png) [@cbrake](https://forum.gitea.com/u/cbrake)\
**Post date:** [August 18, 2022, 2:53pm UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/2 "2022-08-18T14:53:27Z")

</div>

I was just looking at projects as well – is would be useful to be able to create projects at the org level, so that issues from multiple repos could be used in a single project board. Is this possible?

One workaround might be to create an empty repo to hold a project but be able to add issues from other repos to it.

---

<div class="post-metadata">

**Author:** ![cbrake](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/cbrake/32/4809_2.png) [@cbrake](https://forum.gitea.com/u/cbrake)\
**Post date:** [August 18, 2022, 2:54pm UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/3 "2022-08-18T14:54:12Z")

</div>

Custom fields in issues would also be very useful.

---

<div class="post-metadata">

**Author:** ![eeyrjmr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/eeyrjmr/32/1095_2.png) [@eeyrjmr](https://forum.gitea.com/u/eeyrjmr)\
**Post date:** [August 19, 2022, 9:56am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/4 "2022-08-19T09:56:40Z")

</div>

Projects at org level are planned for v1.18 and it looks like it will arrive

> <https://github.com/go-gitea/gitea/issues/13405>
>
> \- Gitea version (or commit ref): 1.13.0-rc1
> 
> \## Description
> 
> Hi, the new Pro…ject 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 https://github.com/go-gitea/gitea/pull/11293#issuecomment-623670239 ).
> 
> I think the most recent status is from this comment: https://github.com/go-gitea/gitea/pull/8346#pullrequestreview-464238421 
> 
> \> - 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,

Likewise pinning issues and repos are planned for v1.18

---

<div class="post-metadata">

**Author:** ![mrall](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@mrall](https://forum.gitea.com/u/mrall)\
**Post date:** [September 5, 2022, 10:14am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/5 "2022-09-05T10:14:29Z")

</div>

no one can answer this question ?

---

<div class="post-metadata">

**Author:** ![Mai-Lapyst](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mai-lapyst/32/5065_2.png) [@Mai-Lapyst](https://forum.gitea.com/u/Mai-Lapyst)\
**Post date:** [September 6, 2022, 7:48pm UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/6 "2022-09-06T19:48:28Z")

</div>

I come from gitlab as well, and being able to nest projects / groups was really neat for organization. Gitea on the other hand replicates githubs stucture, means a flat, one-depth structure.

What I found worked best for me was to think about what scope a project has; if it is something bigger (i.e. a new tool for a customer that possible has many sub-projects or repos) it would get it’s own organisation. If its more a patch thing, i.e. something that stands soly for it, it wanders into a organisation ment to contain many of those small things.

For example I would/do organize my customer as follows:

- Customers that have only one little project get their project stored in a general organisation that is simply named like my workplace with the suffix “customers” (to differentiate it from the org that contains internal repos).
- Customers that have many small or medium projects get their own organisation.
- If a customer has a big project, which propably has its own unique name, it get it’s own organisation; named after the unique name.

Hope I could help you a little bit and give you some ideas how to organize your repos 😃

---

<div class="post-metadata">

**Author:** ![mrall](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@mrall](https://forum.gitea.com/u/mrall)\
**Post date:** [September 7, 2022, 10:39am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/7 "2022-09-07T10:39:25Z")

</div>

Hi, thanks for your answer, especially the “use organisation for bigger projects” gave me a better idea of how to organize things.

cheers

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [September 21, 2023, 6:55am UTC](https://forum.gitea.com/t/basic-concept-of-organisation-repository-milestone-project/5719/8 "2023-09-21T06:55:04Z")

</div>


