ijez a écrit : > Hi, > > Is there any plug-in exits for the mentions subject? > > I'm looking for a way to export my closing ticket into the KB, can someone > show me the way how? > If there're no plug-in exits currently for it, can I ask for features > request for it? > > Hi,
I do not know such a plugin. Just the manual one : CTRL+C / CTRL+V > I'm not good in PHP or any programming, but I'm thinking on the flow like, > if the ticket is done and the user clicking at the close ticket button, > there will be a yes / no popup that asking the user if s/he want to import > the ticket into the KB. If the user select no, then the ticket will be close > as current flow, but if user click yes, the user will be transfer into KB > editing page with all field already fill by populate the closing ticket > likes : > > 1. the category of ticket will be the category of KB, if not exists in the > KB, automatic create the category at the top level (This is much easy if the > ticket category and KB category is the same structure, if not, need to think > more on this), > 2. the title of the ticket will be the title of the KB, > 3. the descriptions of the ticket will be the description of the KB, > 4. the follow-up of the ticket will be the solution of the KB. > Your description is interesting but I do not think that lots of questions / objections mays be done. 1. Linking categories of the tickets and the KB is not so simple to do. 4. Which followup do you want to take as solution ? X. How do you manage rights on the KB ? In which entity do you create your KB ? Your idea may be linked to https://dev.indepnet.net/glpi/wiki/KbTracking (in french but may be rewritten) but need more specifications to be validate before coding. You can also add your ideas on this pages. > Then, the user can add the KB straight away or doing some touch-up first > before adding it. > > So, now the hard part, how hard that will be, to code it in the programmer > point of view with current GLPI version ( 0.71 ). Which file are need to be > edit if I want to shoot it on my feet because I'm think this is more into > the core GLPI and not in the plug-in sections ( integration between ticket > and KB ). > To be integrated in the core, the first step is to write complete specifications which will be validated by the dev team. After, someone (you or someone else) can do the job. Regards Julien > Thanks In Advance, > > Regards, > > > > > > _______________________________________________ > 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
