> > "Tickets". I agree that this is a difficult issue, and I don't think
> > there is an entirely satisfactory solution.
>
> Personally again, I would prefer that any important issues are
> manually moved over... even if that is just referencing a ticket on
> trac. I think this would be valuable to the TiddlyWiki project as a
> way of determining which issues are really really important and
> actionable.

There are tickets in the Trac system that have been repeatedly re-
scheduled to "sometime in a future release", usually as a result of
some short-term priorities at Osmosoft.  This doesn't mean they aren't
important or 'actionable', just that there were other items that were
deemed, at the time, to be more immediately in need of attention.

I *do* agree that new tickets should be created for all actionable
issues.  However, I am greatly concerned that creating a new ticket
that merely *references* a ticket on Trac doesn't ensure that people
actually examine the information in the old ticket and it also assumes
that *only* the referenced tickets are relevant to the current issue.

My concern is that, given how poorly people *currently* use the
information in Trac, I think they are unlikely to suddenly become more
rigorous in checking that information when it is not integrated into
the new ticket system.  There is *always* an "out of sight, out of
mind" effect when information is split across systems, especially if
one of those systems is 'mothballed' for reference-use only and is not
integrated into a single search process that examines ALL ticket
information (both old and new) for related issues.

I also get a sense that there is a desire by some people to simply
ignore and *discard* old tickets and move on without actually
resolving the issues addressed by those tickets, unless they are
*personally* interesting.  It's simply too easy for someone to leave
out the references to old Trac tickets and pretend that those problems
never existed.

As I previously posted, I feel *very* strongly that the existing
tickets should be migrated into the new system (as *read-only*
information) so that the old ticket information is easily searchable
without having to search on two separate systems.  Please note, I am
*not* suggesting that these tickets be made *active* in the new
system.  What I am advocating is that ALL ticket information be
retained and migrated, so that there is no chance that it is simply
"lost" or ignored as a result of the transition.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Reply via email to