Accueil Système de Gestion d'Annomalies
Système de Gestion d'Anomalies PDF Imprimer Envoyer
Le Caviste dispose d'un Système de Gestion d'Anomalies (Bug Tracking System - BTS). Merci d'y reporter toute anomalie, demande d'amélioration ou question.

Comment utiliser le système de gestion d'anomalies

Premièrement, assurez-vous que l'anomalie ou l'amélioration n'a pas déjà été demandée. Tapez quelques mots clés dans la zone de recherche et choisissez "All Statuses" - ceci afin de rechercher également dans les anomalies déjà fermée - votre anomalie est peut-être déjà corrigée :-) 

Si vous trouvez un rapport concernant votre anomallie, n'hésitez pas à ajouter un commentaire ou une pièce jointe si vous pouvez fournir des informations complémentaires. Vous pouvez également vous ajouter à la liste de notification pour être informé par couriel d'un changement sur le rapport.

Si vous ne trouvez pas votre anomalie, utilisez la fonction "Add new task" en haut de la page. Merci de prendre le temps de remplir tous les champs qui vous sont demandés. Merci également de rédigier, si vous le pouvez, votre message en anglais.

Tâches récement ouvertes

  • FS#25: Inventory
    Allow to made an inventory of wine by changing wines quantities and then validate all changes
  • FS#24: Icons for cellar files are missing
    Icons are missing under 2009.1/kde 4.2
  • FS#23: Replace configure script by cmake
    configure is not usable under windows, use cmake in place.
  • FS#22: Can not use key to move in wines list
    When typing a key in the wines list, the cursor moved on wine name not on the first column value.
  • FS#21: Import cellar only works in the presence of XML files which are not exported
    Import file (e.g.) from CSV does not work. Further research shows that:

    1.) The application is trying to read files in /home/jerome/.lecaviste/*.xml
    2.) The current export logic is not creating these files - only the wines table is exported as CSV

    Proposed fix would be:

    1. Modify location of xml files to be $HOME/.lecaviste/ (using getpwent to identify *pw_dir; getpwent seems to be supported in cygwin as well as UNIX)
    2. Add write/overwrite (with safeguards) of all XML files to export function
    3. Identify and document under a new FS number any residual problems with import
  • FS#20: Do not display 0 as millesime
    When a wine as no millesime, 0 is displayed in the millesime column
  • FS#19: Record bin location of wines in cellar
    Wines will be ready to drink earlier if we avoid shaking them up every time we want to get out a bottle of chateau somewhereelse. To this end, I propose adding an //optional// field to the form for adding a bottle, and the form for editing a bottle, that allow the owner to record which bin, rack, and slot the wine is in. This will also require forms to allow the owner to record the physical layout of her cellar. For example, my cellar has three columns of racks: Left, Centre, Right. Each of these columns contains 13 racks, numbered 1 to 13, and each rack contains 6 slots.

    It should also be possible to move "selected" wines. I buy pretty much all the wine for the coming year in November/December. After my children or friends have been to stay for a week, there are gaps in the rack. I can use the space thus created - by consolidating two cases into a single rack - to avoid spending more than necessary of next year's budget on new racks.
  • FS#18: Can not add a wine with no millesime
    Some wine have no millesime defined (e.g. champagne)
  • FS#17: When editing wine appellation with key, country is not changed
    The country is set to the first selected appellation and is not changed after
  • FS#16: Can not read text after zooming on print preview
    The text is unreadable due to aliasing