G2.1 Restructuring

Rework :)

No more nesting of projects, we're re-using the label system!

Because of the complexity of nesting projects, having multiple parents or children en then traversing this graph we are pivoting to a more flat way of structuring our information.

As a start the project will re-create the system most repository managers have. You will be able to view projects, issues and labels all in G2. You will be able to create labels in g2. You will be able to add repositories to a project. This will import all the issues of that repository to the project, as well as the labels. Local labels will then be linked to repo-labels with a 1-1 relation. Optionally suggesting labels that look alike to be linked.

We will create tags, these are the equivallent of former sub-projects. A tag is a label, but a label is not a tag. Tags are more import groups of items. Issues can have all kind of labels. Other items like branches and extra documentation will only be able to have tags.

These items will be imported from their repositories without any tags assigned. You will be able to assign tags to them in the frontend during the creating of a tag or during the linking or syncing of a repository.

Feature ideas

• tags that are children of other tags to still create a sort of nesting?
• creation of a Task, a collection of issues.
• local issues that can be made in g2 and can exist in multiple repo's (like the local labels)