Update home authored by Michael Westergaard's avatar Michael Westergaard
- [Usage](usage/index) - [Usage](usage/index)
- [Planning](usage/planning)
- [Overall navigation](usage/overall-navigation)
- [Installation](installation/index) - [Installation](installation/index)
## Usage ##
I Я Project Manager has many perspectives and they will all make your wildest dreams come true. For a (slightly older) write-up about the underlying ideas + plans, check out [this blog post](https://westergaard.eu/2020/11/gitlab-for-project-managers/).
### Planning ###
Panning perspectives allows planning upcoming or ongoing projects. Planning can work at the global level.
#### Global ####
Global planning allows viewing, creating and managing milestones in projects. Milestones can be colored and grouped using the selection boxes at the top and managed using the Gantt chart itself.
##### Coloring and Grouping #####
The global view supports 3 kinds of colorings: by project, by status, or by load. Each of these supports grouping tasks by tickets or assignee.
Coloring by task looks like this. This is in particular useful to get a very high-level overview of many ongoing projects to to see who is working on what.
![Screenshot_2021-01-13_at_21.30.14](uploads/bfcaa852460a23a461c9aa8c356a06a6/Screenshot_2021-01-13_at_21.30.14.png)
![Screenshot_2021-01-13_at_21.41.21](uploads/9633f8a62a77ca33759879903f9888da/Screenshot_2021-01-13_at_21.41.21.png)
Coloring by status is the default and looks like this. This is in particular useful for assessing the status of individual projects. Closed, Active and Future should be self-evident. Past due means a milestone's end-date has passed without the milestone being closed, and Behind schedule that actual progress does not match up with estimated progress. This mode is of less use when grouping by assignee.
![Screenshot_2021-01-13_at_21.30.28](uploads/401241b68bf545a64e9a83ed878d48b1/Screenshot_2021-01-13_at_21.30.28.png)
Coloring by load counts how many concurrent projects are running per group or per assignee. This allows finding hot spots in projects or when resources might be over-committed.
![Screenshot_2021-01-13_at_21.30.46](uploads/fa2f6546408791943af00815e8d1fa59/Screenshot_2021-01-13_at_21.30.46.png)
![Screenshot_2021-01-13_at_21.41.31](uploads/27b39009f9a6d116c77c4533d017b283/Screenshot_2021-01-13_at_21.41.31.png)
##### Adding/removing/editing Milestones #####
Milestones can be manipulated directly in the chart. Not all milestones can be manipulated (only active milestones) and not in all modes (currently, milestones cannot be manipulated in load coloring or in assignee grouping).
Milestones can be added using the blue plus icon or by dragging in an appropriate swimlane. The plus appears in the project overview on the left for projects only (i.e., not on groups and not on milestone rows).
![Screenshot_2021-01-13_at_21.50.39](uploads/13314afaf295f537e684cff9efdcfc9e/Screenshot_2021-01-13_at_21.50.39.png)
It is also possible to add tasks by clicking and dragging in a project row:
![Screenshot_2021-01-13_at_21.52.56](uploads/36f2b439c1f55e9b8b09674dcb517a1e/Screenshot_2021-01-13_at_21.52.56.png)
Regardless of which method you use, a dialog will pop up allowing editing properties of the task.
![Screenshot_2021-01-13_at_21.53.30](uploads/008cbb7c15b0fa86aa924436510dd89d/Screenshot_2021-01-13_at_21.53.30.png)
Time is measured in working hours with 8 hours per working days with 5 working days a week (Mon-Fri).
Milestones can be manipulated by double clicking on them or by dragging them in the swimlane. When dragged, the duration/period is just changed accordingly. When double clicked, the same dialog shown when creating a milestone is shown allowing either altering the milestone or deleting it entirely.
### Overall navigation ###
#### Different modes ####
It is possible to switch between Project Manager and Developer views using the icons on the top left. This has little utility presently, but developers only see projects with actual milestones.
![Screenshot_2021-01-13_at_21.59.34](uploads/5873fe2569524bf9fcb10e2af0d37080/Screenshot_2021-01-13_at_21.59.34.png) ![Screenshot_2021-01-13_at_21.59.27](uploads/c2c33c3814a0c284aeee9f201d10af5d/Screenshot_2021-01-13_at_21.59.27.png)
#### Manual cache reload ####
The application needs to perform a large amount of web-service calls to display the information. To make this even remotely performant, it uses [very aggressive caching](https://westergaard.eu/2020/12/cacheregistry-improved-near-real-time-caching-of-complex-object-graphs/). The caching can be a bit wonky, so currently, users can manually refresh the cache. This is a temporary workaround and needed if tickets are changed in Gitlab directly or caching for some reason buggers up.
![Screenshot_2021-01-13_at_22.02.51](uploads/07d8f4f1b9d288d48d34f866218eb964/Screenshot_2021-01-13_at_22.02.51.png)
## Installation ## ## Installation ##
Installation is as simple as 1... 2... 3. Installation is as simple as 1... 2... 3.
... ...
......