Define tags (e.g. LP1, LP2,..) and assign them per service
complete
Benedikt Voigt
It should be possible to define tags for phases. For example, the tags for LP1 to LP9, but also tags for acquisition or expenditure phases, could already be predefined.
You should be able to assign tags for each work phase in a project.
Should a phase only have exactly one day (so that clear, disjoint evaluations can be carried out) or several tags per phase (for more flexibility)?
As soon as the tags can be assigned, further features could follow.
For example, evaluations per phase and year:
Which phases produce which result (across all projects, i.e. for the office).
For example, project controlling per phase, if there are several service profiles in the project.
Benedikt Voigt
complete
This point is now closed because the tags can already be defined (the title is now also renamed). The following Canny point is now created for the evaluation itself: https://projo.canny.io/feature-requests/p/auswertung-pro-leistungs-typ-tags-1
Arne Semmler
under review
Arne Semmler
I believe that if it is to be really flexible, then several tags per phase would of course be optimal - but this increases the effort required for continuous implementation in all areas that have to do with services, if, in any case, you would ideally also want to define deployment budgets per “day” within a project, would like to book working time on “tags” or do deployment planning on “tags”. If “tags” were only for evaluation (i.e. as a kind of sorting criterion), multiple “tags” per service would not be a problem; if you want to think of the above-mentioned extended approach, several tags per service could become problematic, since the same performance would then occur several times.
M
Martin Exler
It would be great if it worked out. I have also already been asked about this by the GF.