Kolab Issue Tracker
From Kolab Wiki
Technical issues and requests for enhancements for Kolab components can be reported to the Kolab Issue Tracker. The tracker provides encrypted connections (https) using self-generated SSL certificates, so you may want to import Intevation's CA certificates to access it in a secure way.
If you experience a problem with one of the Kolab components, you may want to check if the tracker already has an entry for this as sometimes solutions or workarounds are already documented there. If you do not see a corresponding entry, you can create an issue.
How to create an issue?
To create new issues and to add comments or subscribe to existing issues you have to register with the Kolab issue tracker.
Please specify the versions of the software you use (e.g. "Kolab Server 2.2.1 on Fedora 10") and other details (e.g. error messages and steps to reproduce the problem) in order to provide the developers the necessary basics to actually solve the problem.
Here are some predefined links to report problems with specific Kolab components:
- Kolab KDE client (Kontact enterprise5)
- Kolab KDE client (Kontact enterprise35)
- Kolab KDE client (other kontact versions)
- Kolab web client (Horde)
- SyncML part of the Kolab web client
- Kolab server
- Kolab server: web admin interface
- Kolab server: mail filter
- Kolab server: freebusy handling
- not sure or anything else
Notifications for new issues are sent to the kolab-devel mailinglist, while messages added to existing issues are only sent to the people listed in the "Nosy List" of that issue. You can add your Roundup user name to the Nosy List to subscribe to new messages for an issue.
You will be assigned the role "Provisional User" by default. This means you can edit all fields of issues you have created yourself, for other issues you can just subscribe/unsubscribe and add messages or attach files. To be able to change the title, nosy list, assigned-to field or keywords of all issues or to post merge entries you need the role "User". Just ask on one of the mailinglists (kolab-users or kolab-devel) and include your roundup user name in the request.