1 |
On Thursday, March 30, 2017 2:41:02 PM EDT William L. Thomson Jr. wrote: |
2 |
> On Thursday, March 30, 2017 2:34:56 PM EDT Kent Fredric wrote: |
3 |
> > _Especially_ when a developer marks a ticket as that without adequate |
4 |
> > explanation as to why. |
5 |
> |
6 |
> That sounds like the problem. Do not rely on status/keywords alone. Anytime |
7 |
> those change, a comment should be included as to why. That seems like it |
8 |
> would clear up much of the confusion. Simply do not change status/keywords |
9 |
> without a comment to briefly explain the change and/or usage. |
10 |
|
11 |
It may even be possible to force this pragmatically. Require a comment with |
12 |
any status/keyword change via code. Form submit validation requirement. That |
13 |
way no one can get around it. It also does not require further enforcement, |
14 |
social or otherwise :) |
15 |
|
16 |
-- |
17 |
William L. Thomson Jr. |