On Jun 28, 2018, at 6:15 AM, David Mason <dma...@ryerson.ca> wrote:
> where did you make these changes?

It’s most readily seen in this repository:


In addition to the reporting changes I previously described, there are others, 
mainly in Admin > Tickets > Common.  For instance, my resolution_choices list 
includes the nonstandard “Implemented” choice, which I use instead of “Fixed” 
when I finish implementing a feature request ticket.

Further thoughts on this topic:

Features do sometimes jump multiple levels.  For instance, an idea that was 
once just a good idea — “Medium” in my system — may eventually be deemed 
essential and thus jump straight to Immediate priority.

Features sometimes also fall multiple levels.  A person filing a feature 
request might have what he thinks is a really hot idea (“High”) but when we 
later go through the release planning exercise, management may think it’s a bad 
idea for some reason, so it drops to Low rather than being deleted.  We may add 
a comment on reprioritizing at this point to record who spiked the idea, so we 
know who has to be convinced if the idea comes back up again.

The High priority pool rarely drains, even immediately after planning the next 
release.  We have more great ideas than time to implement them.  We just hope 
to get to those ideas before the world changes enough that the feature ideas 
become worthless, in which case we need more developers: we’ve left fruit on 
the tree.

The Medium pool never drains until the project planners run out of good ideas, 
at which point it’s time to mothball the project.

If the Low pool ever drains, it probably means you’re not capturing enough of 
the organization’s knowledge in Fossil.  After enough member turnover, the 
organization will forget things it should remember.

“Low” may be an idea graveyard in a private repository, but in a public repo, 
it is where features that the core developers are unlikely to get to land.  
This pool is a good place to point outside contributors, since they’re ideas 
worth keeping but they’re unlikely to conflict with a core developer’s plans.  
That’s not an exclusive characterization: Medium will have more such ideas, 
just with a higher risk that some core developer has his eye on it and has 
plans to get to it someday.

Fossil’s ticketing system is really quite flexible.  There’s a good chance you 
don’t have to accept things you don’t like about it: the fix might be easily 
fossil-users mailing list

Reply via email to