Hi, can someone please explain how "Priority" works, as it determines how soon a task is fixed. What is the meaning of "reflects reality and does not cause it"? Thank you.
Topic on Talk:Phabricator/Help
Jump to navigation Jump to search
@Akmaie Ajam Hi, see Phabricator/Project management#Setting task priorities - thanks!
@AKlapper (WMF) Well, why https://phabricator.wikimedia.org/T210224 has Medium priority, while https://phabricator.wikimedia.org/T172838 has Low priority, even though they are similar (removing/replacing FlaggedRevs)?
@Akmaie Ajam: T210224 is a discussion about reverting T121995 which happened in 2015. It might have a different priority because someone has decided to work on T210224. In any case, the "Priority" field often does not change much, and sometimes is "wishful thinking" what we would like to avoid. Whether someone plans to work on a task is more relevant.
So, the task priority stays on Low (or Needs Triage), no matter the actual priority/importance, until someone decides to work in the task?
@Akmaie Ajam Priorities or "importance" for you or a community unfortunately can differ from priorities of the limited number of developers, or priorities which need to balance the needs of hundreds of Wikimedia communities.
If you think that there are reasons why a certain task should have a higher priority compared to the priorities of many other open existing tasks out there, feel free to elaborate in the corresponding task. Thanks! ( Furthermore, raising the priority of a task won't change anything, as long as nobody plans to work on a task, but I guess I explained that before.)
What is the definition of "affects normal, everyday work significantly" and "contrived examples or problems that only appear under unlikely circumstances"? Does FlaggedRevs meet the former or the latter criteria? (Note: It affects the unregistered readers, which makes up most of users of Wikipedia)
There is no priority for "affects normal, everyday work significantly" as that's not describing priority (urgency) but describing impact (severity). These are different things...
No, what I mean is the aforementioned question in Bug management/Phabricator etiquette.
I don't think I can provide a clear "definition" for what you wrote. In my understanding of the term "definition" it is already a definition.
What I mean is the line in Bug management/Phabricator etiquette that says "Report status and priority fields summarize and reflect reality and do not cause it." and "Contrived examples or problems that only appear under unlikely circumstances are generally evidence for treating the problem as "low" or "lowest" priority, since the limits of any non-trivial software can be exceeded if you try hard enough."