Those are currently priority "normal". But what do we use the priority field for at the moment anyhow? Mostly it's set to "normal".
Can we developers use it perhaps the priority field for some kind of "high means, should be done as fast as possible" [because it would otherwise block a point release or otherwise make someone else's task harder than necessary]? For easy tasks such as "add package xyz with signed tag to repository"?
What I find not useful on most bug trackers is users bickering about priority "high means important". By that logic, we would never get to work on the priority "normal" tasks.
So I hereby suggest extra fields:
- severity: Describing the impact. For example T203, T207, T31 could be declared that they might have a "high" impact. I.e. those could significantly increase security. Alternatively we could call it "impact" rather than "severity".
- difficulty: Based on our current team and/or time requirements we estimate, we could also say for example T203, T207, T31 have difficulty "high". Not sure if the difficulty field would be any useful or rather deterring?
- we keep leave it as is
- we also remove the "priority" field
- something else