Bug reports
bugreports


EGroupware bug tracking system

No Software is free of Bugs - I'm sure you know ;-)

If you find a bug in eGroupWare, we would like to know about it.

To systematic remove all bugs from EGroupware we use this bug-tracking-system.

Please make sure you have read "how to report bugs" below!


 
showing 1 - 15 of 284
Select columns














Category Version Summary Date opened ♦ Not closed All
Votes
Actions
Calendar Version 1.6.003 Regression - Calendar dosen't send emails to participants 2007/11/16 14:18 Open Fixed 8
FelamiMail Version 1.6.003 Felamilail stores clear passwords in DB 2009/01/08 10:54 Open None 6
SyncML Version 1.6.003 funambol, iphone and two way sync 2009/01/16 10:20 Open None 6
Admin Trunk Error in the view error log application 2007/02/28 21:32 Open None 5
Calendar Version 1.6.003 Participants status does not change when moving event 2009/02/24 15:12 Open None 5
GroupDAV Trunk GroupDAV ignores username in url when adding calendar events 2009/10/14 13:52 Open None 5
Calendar Version 1.6.003 Alarms on recurring events 2008/11/19 16:53 Open None 4
Bookmarks Version 1.6.003 No back 2009/02/12 23:51 Open None 4
SyncML Trunk funambol fails to upload email address 2009/03/18 17:14 Open None 4
GroupDAV Version 1.6.003 Fehlerhafter CalDAV sync bei iPhones mit EGW 2009/10/01 10:40 Open None 4
Calendar Version 1.6.003 Mail all participants -dosen't fill in members of groups 2007/07/04 13:22 Open Fixed 3
API Version 1.6.003 Expired user account still shown. LDAP backend. 2007/07/10 11:23 Open None 3
Calendar Version 1.6.003 csv export custom fields 2007/10/18 13:06 Open None 3
SyncML Trunk Adressbook Sync should add Contacts "private" as default 2008/11/21 19:56 Open None 3
Resources Version 1.6.003 Attaching Files to Resources doesn't work 2009/04/07 18:10 Open None 3
 

How to report bugs

What to do if you find a bug?

  1. Update your installation to the latest version (of your release) or try to reproduce the bug on our demo site which is up to date. The bug might be already fixed.
  2. If not, check if there's already a bug reported. Bugs reported double, consume time from the developers, they can not spend in fixing bugs or developing new features.
  3. If not, open a new bug and provide the following information:
    • in which eGW application does the bug occur (Category)
    • a short and pregnant summary about the bug (eg. 'edit addressbook entry gives error-message while saving')
    • the eGW release you use (Group)
    • a detailed description about the bug: It can't be repeated often enough: the more detailed your description is, the easier a developer can reproduce the bug. Without being able to reproduce a bug there's nearly no chance to fix it. Even if you think it's absolutly easy to reproduce, it might be not. It can depend heavily on your configuration and data. So please 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 webserver (incl. versions) you use
      • a step by step description on how to reproduce the bug, like you want to explain it to your parents ;-)
  4. Please respond in time to questions the developer might have. These questions will be automaticaly 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.
Thank you very much

your eGroupWare team

Stylite GmbH


Stylite GmbH - The main developer of EGroupware

EGroupware 2010



Login

Login Name

Password

remember me

Sourceforge.net


SourceForge.net Logo