How Tos
We're not happy with the input fields that goes with every issue so we want to add some extra custom fields to collect the users details.
Set up custom fields to your issuetracker
06 Jul 2008
We're going to show how you can run the integration tests (aka. unit tests) on your own system. This can be very helpful for helping out with reporting bugs.
Run the integration tests
28 Apr 2008
If you want to customize the way issues are added without rewriting the code you can use the two hooks pre_SubmitIssue and post_SubmitIssue.
Using pre_SubmitIssue and post_SubmitIssue to customize issue adding
11 Feb 2008
By default the IssueTrackerProduct sends out notifications as soon as they're created. By delaying that you can avoid sending out notifications to people who don't need them.
Setting up cron on Linux to send out delayed notifications
02 Feb 2008
Monitor multiple issue tracker instances from one place. This how to shows how to set that up in the Advanced Properties.
Join-in issue trackers
10 Jan 2006
If you are familiar with writing Issue Tracker Report Scripts you might need to pass a variable to the report script that changes every time such as dates or other booleans. This How to shows how to accomplish that.
Run reports with changing variables that can't be set statically
25 Oct 2005
Perhaps you're using the POP3 support in your issuetracker instance but feel uncertain about how to set up the crobjob. This howto shows you how to set up a crontab on Linux.
Set up cronjob to periodically check for inbound issue emails
20 Oct 2005
Suppose you have an IssueTrackerProduct instance where you discuss bugs and issues on a piece of software or a website. For the sake of security you have switched off public access but you still want to accept feedback from the public. What do you do?
Ability to let people add issues without revealing your issuetracker
12 Oct 2005
Every status an issue can be in sort of corresponds to a value of progress. This howto explains how to enable a calculation of an "overall status progress".
Overall status progress
11 Jul 2005
When listing issues, there are by default two ways: rich and compact
By enabling an advanced properties you can have a third way: CSV
Enable CSV export link
01 Jul 2005
Issues are shown in two places. One is when you click an individual issue and one is when you use the Complete List. What do you do if you temporarily don't want to show any of the followups?
Hide followups
30 Jun 2005
There are two ways to export issues to CSV. This howto explains the basic way.
Export all issues to CSV
30 Jun 2005
Suppose you have a stylesheet (locally or globally) that you want to show any issuetracker page with, what do you do?
Use a forced stylesheet
13 Jun 2005
If you have a lot of issues and a lot of people working on an issue tracker it is common to refer to issues by they number (aka. ID). Here's a simple hint on how to enable that.
Showing the number of the issue next to the title
21 Apr 2005
Or, how to not use
Programmatically getting issues
06 Apr 2005
objectValues(), objectIds() or objectItems()
By default the Id of your issues look like this "0001" or "0193". What if you want them to look like "1" or "9".
Really short issue Ids
16 Mar 2005
This how-to shows an example way of writing your own customisations to the IssueTrackerProduct as a Zope Python product.
Monkey patching the IssueTrackerProduct
10 Mar 2005
