Thanks for answer, MoYo! >For 0.80 features which are already planned, donations to the project >will speed up the development.
What amount of financial help can raise priority of 1) and 2) tasks (email problems)? Now 1) is the most important problem for me - current mail parser and huge unreadable emails make users very unhappy ))). As I understand, this tickets should solve this problems: https://forge.indepnet.net/issues/show/1142 https://forge.indepnet.net/issues/show/848 Of course, we will help with testing. >> 3) Ability to assign messages from existing in GLPI users to user & to >> entity user belongs to. >> >Could you explain more that you mean ? User A belongs to entity B. Ticket from user A via email should be assigned both to user and to entity (at least if user belongs to only one entity - it's quite common). >> 4) Accurate reminders to tech support about unassigned tickets. >> >What do you mean exactly ? I should think more on this topic. On other questions I'm going think more and write to forge. Wrote a bit already - https://forge.indepnet.net/issues/show/1324 -- Savchuk Taras -----Original Message----- From: glpi-dev-boun...@gna.org [mailto:glpi-dev-boun...@gna.org] On Behalf Of MoYo Sent: Thursday, September 10, 2009 11:51 PM To: Liste de diffusion des developpeurs GLPI Subject: Re: [Glpi-dev] Tickets/task separation, preconfigured filters, tickets/email improvements Тарас Савчук a e'crit : > The complete answer :) > I'm very interested in implementing: > > --- Email integration --- > > 1) Good email parser both for HTML and plain text messages (no > problems with missing/added new line characters, no encoding > problems). Some of problems was discussed here - > http://www.glpi-project.org/forum/viewtopic.php?id=12378 > A ticket is planned for tha 0.80 version : https://forge.indepnet.net/issues/show/1142 We have several libraires to test. If you want to test them you are welcome. > 2) Templates for messages with sensible lightweight defaults (we can > learn from Zendesk here). For example, there is no need to send all > ticket body to user -- we can simple send message with "You ticket > with subject <message Subject> received. Ticket number is #. Our > technician will be working on it shortly". > This is an already planned ticket : https://forge.indepnet.net/issues/show/848 Now it was planned for the 0.95 version but may be moved to the 0.80. We have several contributions (see in user wiki) and must work on it. > 3) Ability to assign messages from existing in GLPI users to user & to > entity user belongs to. > Could you explain more that you mean ? > 4) Accurate reminders to tech support about unassigned tickets. > What do you mean exactly ? > --- Tickets --- > > 1) Separation of tickets & tasks (it's done in Zendesk). Tickets are > subject of SLA, tickets need to be resolved/assigned quickly. Tasks > may have one important field -- due date (or due date + start date). > Task can be open in GLPI for any amount of time, it's not subject of > SLA and viewing of tasks can be easily separated from viewing of tickets. > All these features are already planned : SLA : https://forge.indepnet.net/wiki/glpi/GlpiSla Review Ticket Usage : https://forge.indepnet.net/wiki/glpi/RefonteAffichageTicket with mockups > 2) Time management improvements. Now planned ticket time = t(planned > finish) -- t(planned start). It's completely senseless: or we don't > use planning or we can't count time correctly. We must be able to > input spent time manually or planning can only be used with tasks > (tickets by nature need short-term actions). > You could see a mockup here : https://forge.indepnet.net/attachments/15/Taches.png > 3) Predefined/configured filters for tickets, i.e. with one click we > must be able to view "today tickets", "this week tickets", "unassigned > tickets", "my tasks"... Big filter panel can be completely hidden. > You could already use bookmarks to do such a think. Search Engine for tickets will be changed : https://forge.indepnet.net/issues/show/1123 > --- Documentation --- > > 1) Per-entity wiki for collaborative work on entity's documentation. > I do not think what the aim of GLPI is to include a wiki system. > > I consider to allocate some financial help for improvements to be done > in such/similar directions :) > > As I understand, Denis Linvinus are thinking in similar way. > For 0.80 features which are already planned, donations to the project will speed up the development. Regards Julien Dombre _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
