What is the challenge? |
We have many types of requirements and today it is hard to quickly see the difference between them or report on the number by type. |
What is the impact? |
Less efficiency and consistency. We use a workaround of placing emojis in the requirement name and also adding tags to the requirements. This takes time and is hard to remember to do. If we forget, it is then hard to quickly identify bug requirements or report on the number of bugs found per feature, for example. |
Describe your idea |
Requirements support a "type" field just like features do. Show the type icon on the requirement and allow reporting by requirement type. Requirements may need their own list of types separate from the list of feature types, but we could probably start with a shared list. |