| Version 16 (modified by chris, 23 months ago) (diff) |
|---|
Table of Contents
Transition Trac Tickets and Wiki
This Trac server is running on wiki:PenguinServer#tech.transitionnetwork.org.
This Trac site can be administered via the admin interface.
You can test things on the SandBox page.
See ticket:819 for issues related to email spam and Trac.
Trac Documentation
- TransitionTrac -- starting place for Trac information
- TracUserAdmin -- adding user accounts to Trac
- TimingAndEstimationPlugin -- the time tracking extension
- DevelopmentServer#Trac -- install notes for DevelopmentServer
- TracGuide -- built-in documentation
- TracSupport -- Trac support
Time Tracking
Time worked can be added to tickets and ticket comments, to produce a report on the time spent for a period:
- Set a "New Bill Time" using the form element at the bottom of the Management page, the format is YYYY-MM-DD HH:MM:SS, eg 2013-04-30 23:59:59
- Select a "Start Date" and "End Date" on the Management page and then click the "Developer Work Summary" link in the "Billing Reports" list.
- To see a more detailed list of the work done during a month you can use the Timeline, eg May 2014 Timeline (note the date format is mm/dd/yy).
External resources
- The Trac project -- Trac Open Source Project
- Trac FAQ -- Frequently Asked Questions
Tickets
Open Trac tickets:
Closed Trac tickets:
Install Notes
This Trac site was originally installed via ticket:1, there is also a ticket for enabling incoming email so that tickets could be updated via email, ticket:3 and one for adding time tracking to commits, ticket:179. See also the notes on migrating trac from the DevelopmentServer to PenguinServer, ticket:470#comment:27.
Default Ticket Settings
The default owner for tickets has been changed on ticket:597 and how to do this and also how to set the default Component etc are on that ticket.
Fetchmail
Email was configured on ticket:494 and when the mails server SSL cert is changed it's fingerprint needs updating, see ticket:494#comment:21 and ticket:750, these are the steps that need to be followed when the cert at mail.webarch.net is updated:
Check for this issue:
su-trac fetchmail fetchmail: mail.webarch.net fingerprints do not match! 140106143241896:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:1172: fetchmail: SSL connection failed. fetchmail: socket error while fetching from trac.tech.transitionnetwork.org@mail.webarch.net fetchmail: Query status=2 (SOCKET)
Get the new fingerprint:
fetchmail -v -p imap -u trac.tech.transitionnetwork.org mail.webarch.net | grep -i "key fingerprint" fetchmail: mail.webarch.net key fingerprint: EE:E3:86:28:53:FB:E9:C4:97:68:C7:43:11:CA:CC:6C
Update /web/tech.transitionnetwork.org/.fetchmailrc with the new fingerprint and test:
fetchmail 22 messages for trac.tech.transitionnetwork.org at mail.webarch.net. reading message trac.tech.transitionnetwork.org@mail.webarch.net:1 of 22 (2047 header octets) (2041 body octets) flushed reading message trac.tech.transitionnetwork.org@mail.webarch.net:2 of 22 (1284 header octets) (10980 body octets) flushed reading message trac.tech.transitionnetwork.org@mail.webarch.net:3 of 22 (1284 header octets) (10332 body octets) flushed ...
