EGroupware community tracker
Login below to report bugs, add feature requests and submit patches
What to do if you find a bug?
1. Update your installation to the latest version. The bug might be already fixed.
2. Check if there's already a bug reported!
3. If not, open a new bug and provide detailed description about the bug. State at least:
-- which version of EGroupware and the according app you use (see the about-page of the app)
-- which php version you use and if you have register_globals set to off (recommended for security reasons) in your php.ini. (Admin-> PHP information gives you the necessary details)
-- which database-type & version you use
-- which OS and web server (incl. versions) you use
-- a step by step description on how to reproduce the bug4. Respond in time to questions the developer might have. These questions will be automatically mailed to you via sourceforge.net. Therefore it's an absolute requirement that you provide a working email address, either by login into sf.net or by providing one in the bug-report.
EGroupware feature request
We appreciate if you help us to improve EGroupware :-)
Please check the already made requests before you add a new one. You can vote for requests to support them. If you blindly add a new request, you lower the chances to get it implemented (because it has no votes)!
If the feature is important for you, you might want to consider sponsoring the feature. Please contact info AT egroupware DOT org to do so.
EGroupware patch manager
It's important to describe what your patch is going to archive and against which eGW version you made it. Patches should be made as unified diffs, if possible with svn diff against an up to date eGW version.
The released version (at the moment 1.8.xxx) only receives bugfixes and new translations, new features always go into the development version aka trunk.