We agreed that the Severity information would be printed in the task description, since we decided not to have such field in Phabricator. Currently this information is missing in bugzillapreview. See for instance https://bugzilla.wikimedia.org/show_bug.cgi?id=57540 (Severity: critical)
|· · ·|
|Resolved||chasemp||T552 https://bugzillapreview.wmflabs.org/ migration preview instance|
|Resolved||Qgil||T695 Severity information is not being migrated|
|· · ·|
- Mentioned In
- rPHTOd93501eb407c: fixes migration concerns
T694: Print URL, Version, etc only when they contain data
- Mentioned Here
- T552: https://bugzillapreview.wmflabs.org/ migration preview instance
T259: Bugzilla to Maniphest import script (tracking)
T102: Decide whether we need to add a severity (impact) field to match Bugzilla's
I would not migrate Severity as a custom field, but as a searchable text string in the task description.
However, T259: Bugzilla to Maniphest import script (tracking) says
Severity: To be dropped, T102
and consequently, https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated says
Severity - Not migrated
Considering that we agreed that the latter is the canonical reference, the script works as specified. However, I believe something got lost in the requirements? If we add "Hardware/OS" to the description, we might as well add Severity.
The Severity field is gone for good (and yes, we can document better this fact). This task is simply about adding to the description the Severity value of the Bugzilla reports imported.
I understood that it would be replaced with project board prioritisation. If that's not going to be automatically filled in it's going to be a serious pain. I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
What do you want t do with this information? If you want to search candidates for next sprints, and you want to use the Severity information to help you, you could always query tasks in project X with the string "Severity: Critical", and that should provide you the sample you are looking for.
I don't think workboards are the right tool for this task. Are you planning to have a VisualEditor workboard where each column corresponds to a severity level? Besides, Workboards are good to handle dozens of tasks anyway, not hundreds.
Good catch, sorry for the inconsistency. Let's drop the string values of "severity" (and "whiteboard" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
Clueless cargo cult patch in https://gerrit.wikimedia.org/r/#/c/167548/
I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
I would recommend at some point rather sooner than later to (mass-)prioritize those open VE tickets in Bugzilla with Priority=Unprioritized even if that would only be a rough categorization (e.g. set Priority=lowest for open tickets with Priority=unprioritized && Severity=enh|trivial|minor and Priority=low for Priority=unprioritized && Severity=normal|major or whatever works). Otherwise you will end up with a large list of "Needs triage" tickets after the Phab migration. Also note that Target Milestones will be migrated which offers another way to plan.
I'm having issues trying to reconcile contradictory indications:
Let's drop the string values of "severity" (and "whiteboard" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
(apparently done) vs.
you could always query tasks in project X with the string "Severity: Critical"
What's the current status? Are we sure that users were actually able to understand how the imported tasks will look like as regards "Severity", even though the import was changed after the bugzilla preview? (Cf. T552 which declined the creation of a final preview.)
So, if the others are triaged, this leaves us with 568 triaged tickets which received a non-default severity. https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=minor&bug_severity=trivial&bug_severity=enhancement&list_id=359859&priority=Immediate&priority=Highest&priority=High&priority=Normal&priority=Low&priority=Lowest&product=OOjs&product=OOjs%20UI&product=VisualEditor&query_format=advanced&resolution=---
How is that triaging work being preserved?
Reopen because [[Phabricator/Help]] is silent on severity and [[Phabricator/versus Bugzilla]] only says «Also note that Severity, Version, URL, Whiteboard, and other fields will not be available in Phabricator, because we have decided to discontinue them. The related data available in Bugzilla reports will be added to the description of the task.» Users need documented workarounds to access the information in question, such as the translation between previous and future values that Aklapper implied in https://phabricator.wikimedia.org/T695#12650
I'm not sure I understand your request. So the only problem here is that you expect that the "Severity: " text string is documented in /versus_Bugzilla, reflecting all the possible values, including the case where it is unspecified, right?
I expect the answer to be
I will ask.
The way to retrieve this information is a search query.
Available Severity values in Bugzilla are
and there is no conversion; this will just be added to the task description in Phabricator. Severity cannot be unspecified.