How many tickets are we talking about? If it is only a few then perhaps try the following:
# Set your system date to the date for the ticket sudo date -s "08/11/2011" # create the ticket fossil ui # repeat for remaining tickets Maybe do it in a virtualbox instance just be sure to put the date back to where it should be before syncing. On Fri, Sep 2, 2011 at 11:10 AM, Ron Wilson <[email protected]> wrote: > On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen <[email protected]> > 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. So it > > seems like you could add your own field for storing your custom > timestamp, > > and update your ticket reports to reference/include the custom field. > You'd > > probably need to do whatever validations you need in client-side > javascript. > > I think there's info in the Fossil Wiki about adding custom fields. > > 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. 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? > > I think that the Ticket Entry page could be enhanced with Javascript > to submit a new event to Fossil. At least when I created an event and > used the submit button (rather than the preview button), the response > from Fossile was a simple acknowledgement, so the Javascript would not > have to do more than parse the response for any errors messages and > display those errors, if any. > > The event summary would be the ticket summary and the even body could > be a link to the actual ticket. Possibly the Fossil Header could use > some combination of TH1 and Javascript to actually include the > contents of the ticket. > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
