Open brendoncaulkins opened 5 years ago
From the PO: Tagging skills would add a lot of use cases, i.e. tagging skills with a project name so someone knows what skills needed for a project. This is purely a functionality enhancement though so anything that adds to components that don't already exist in the app should be done first.
Tagging would be like adding a label to a skill (and many could be added). For example, if the skill is javascript, then you could tag that with "Project XYZ" and repeat with other skills, so later you could find what skills are needed for that project. You could also tag skills with things like "API developer", "senior developer", and such so you know what skills to focus on to get into a given role. There are many other opportunities with this kind of functionality.
Per Wyn - changed this to V3, as long as you have a full workload in V2. If room becomes available in V2 - then you can pull this in.
From the PO: Tagging skills would add a lot of use cases, i.e. tagging skills with a project name so someone knows what skills needed for a project. This is purely a functionality enhancement though so anything that adds to components that don't already exist in the app should be done first.