Move all Project Boards from Organization Level?

[Davidezrajay]

Where to have the Project boards
Main Goals

1. Outside collaborators show up, and immediately find a task that is both important and something they want to work on.
2. Always have a grasp on the next critical issue.

Keeping all in Projects Boards at the Organizational Level

• Can add up to five Repositories to a project
• Pro = It is all in one place, easy for PM
• Con = Not visible from Development Overview Repo

Main Organizational Level

We currently have:

• CI/Cd project
• An everything project in the org
• Android Project

Individual Repository Level

We currently have:

• Admin Panel (Organized)[https://github.com/Greenstand/treetracker-admin-DEPRECATED]

Zenhub

Not really used

[Davidezrajay]

From jgonggrijp
at my work, we use the “automated kanban with reviews” flavor purely because it hast the most options; we remove some of the columns and change the automation settings directly after creation. If you create the board at the organization level, you can add issues to it from all repositories. You can switch off the automation that puts new issues in “to do”; if you do so, new issues that you add to the board will be added to the triage list instead, which can be used as a backlog. Issues not manually added to the board appear below the triage list (right menu). In that part of the list, you can prioritize some repositories by making them “associated” with the board. That’s all the tips I have!