-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
-
None
Once SKARA-1912 has been integrated (great work Zhao!) and stabilized, I think we should look into adding labels to the pull requests corresponding to the issue type and and priority. For example, if a PR solves an issue with type "Bug" and priority "4" we add the labels "bug" and "P4". We, and most projects on GitHub, use lowercase for labels, but for priorities I think we should make an exception (everyone are so used to seeing "P3" compared to "p3").
If a PR solves multiple issues, then we add a label once for each type of issues solved (although rare a PR could solve both an "Enhancement" and a "Bug"). As for priorities we should only add the highest priority, so if a PR solves a "P2" bug and a "P3" bug we only add the "P2" label.
To summarize I would suggest the following mappings to labels:
- Issue types
- "Bug" -> "bug"
- "Enhancement" -> "enhancement"
- "JEP" -> "jep"
- "CSR" -> "csr"
- "Task" or "Sub-task" -> "task"
- Priorities
- "P1" -> "P1"
- "P2" -> "P2"
- "P3" -> "P3"
- "P4" -> "P4"
- "P5" -> "P5"
If a PR solves multiple issues, then we add a label once for each type of issues solved (although rare a PR could solve both an "Enhancement" and a "Bug"). As for priorities we should only add the highest priority, so if a PR solves a "P2" bug and a "P3" bug we only add the "P2" label.
To summarize I would suggest the following mappings to labels:
- Issue types
- "Bug" -> "bug"
- "Enhancement" -> "enhancement"
- "JEP" -> "jep"
- "CSR" -> "csr"
- "Task" or "Sub-task" -> "task"
- Priorities
- "P1" -> "P1"
- "P2" -> "P2"
- "P3" -> "P3"
- "P4" -> "P4"
- "P5" -> "P5"
- is blocked by
-
SKARA-1912 Show priority for bugs in pull request body
-
- Resolved
-