At 11:10 AM 9/2/2011, Ron Wilson wrote:
>On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen wrote:
>> FWIW, Fossil does allow you to add fields to the ticket table,
>> markup to the ticket create/edit/view pages, and customize the
>> ticket reports.....
>
>Yes, I've added custom fields to tickets and made reports that
>sort on those fields.
>
>However, the the request is to be able to have the ticket's first
>appearance on the Time Line view correspond to the date/time the
>requester sent his/her message, rather than the time the project
>maintainer entered the ticket into Fossil.
Exactly.
>Maybe the ticket entry processing could be enhanced to
automatically
>create an event in the case that a ticket's submission
date/time is
>earlier than it's creation date/time?
Even simpler would be to include the ticket's creation date as a
field on the new ticket entry form, pre-filled to "now", instead
of it being a system-generated field that is not shown to the
user. From a user standpoint, this would look just like the date
entry on the New Event page, and could work similarly. I'm not
sure it really needs any validation, but it would make sense to
prevent the creation of a ticket in the future if that were trivial.
This would satisfy my needs for new batches of bug reports, and I
can live with the current state for all those already entered.
The downside of this is that there is no way to edit the ticket
time once the ticket is submitted, which could be needed if a
gross typo were made.
I'm just trying to avoid the strong temptation to deconstruct the
repo, edit the offending ticket's artefact's D record by hand, and
reconstruct....
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
+1 626 351 1590 FAX
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
