Your comments

Hello Johan,


I'm glad you like the idea. ;)


Actually I'm not talking about to add or include all the most used languages but only a selection of them; those that are worldwide used for their importance, that are more interesting for GLPI Project and that are completely translated in transifex. In a nutshell, and regarding GLPI 9.2.x, I'm talking about English (en-GB | en-US), Spanish (es-ES), French (fr-FR), Russian (ru-RU) and German (de-DE).


And not, I'm not talking about to do that automatically (or automagically). :)


Regards,

Good morning,


I have detected mistakes into Suggestion #1, Suggestion #2 and Suggestion #3.


Mistake into Suggestion #1
  • Massive Actions for Assets
    • Associate with Ticket...
    • Associate with Problem...
    • Associate with Change...
    • Associate with Problem...
    • Associate with Knowledge Item...

   It should be...


  • Massive Actions for Assets
    • Associate with Ticket...
    • Associate with Problem...
    • Associate with Change...
    • Associate with Project...   <----------------------(***fixed***)   
    • Associate with Knowledge Item...

"Associate with Problem..." is repeated.


Mistake into Suggestion #2


  • Assets
    • 'Tickets' tab  
      • Associate with Ticket...
    • 'Problems' tab
      • Associate with Problem...
    • 'Changes' tab
      • Associate with Change...
    • 'Problems' tab  <-----------------------------(***This tab is missing***)
      • Associate with Problem...
    • 'Knowledge base' tab
      • Associate with Knowledge Item...

It should be...


  • Assets
    • 'Tickets' tab  
      • Associate with Ticket...
    • 'Problems' tab
      • Associate with Problem...
    • 'Changes' tab
      • Associate with Change...
    • 'Projects' tab  <-----------------------------(***This tab is missing***)   <----(***fixed***)
      • Associate with Project...   <-----------------------------------------------(***fixed***)
    • 'Knowledge base' tab
      • Associate with Knowledge Item...

"'Problems' tab > Associate with Problems..." is repeated.


Mistake into Suggestion #3


  • Assets
    • 'Tickets' tab  
      • Create a  new Ticket for this asset...    (***It already exists***)
    • 'Problems' tab
      • Create a new Problem for this asset...
    • 'Changes' tab
      • Create a new Change for this asset...
    • 'Problems' tab  <-----------------------------(***This tab is missing***)
      • Create a new Problem for this asset...
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this asset...

It should be...


  • Assets
    • 'Tickets' tab  
      • Create a  new Ticket for this asset...    (***It already exists***)
    • 'Problems' tab
      • Create a new Problem for this asset...
    • 'Changes' tab
      • Create a new Change for this asset...
    • 'Projects' tab  <-----------------------------(***This tab is missing***)   <----(***fixed***)
      • Create a new Project for this asset...   <-----------------------------(***fixed***)
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this asset...

"'Problems' tab > Create a new Problem for this assets" is repeated.


Please take these mistakes into account. Best regards.


Good night,


I was thinking that maybe there could be room for another suggestion; it is the next.


Suggestion #3 > Make bottom-up objects

It should be created the following new actions.


  • Assets
    • 'Tickets' tab  
      • Create a  new Ticket for this asset...    (***It already exists***)
    • 'Problems' tab
      • Create a new Problem for this asset...
    • 'Changes' tab
      • Create a new Change for this asset...
    • 'Problems' tab  <-----------------------------(***This tab is missing***)
      • Create a new Problem for this asset...
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this asset...
  • Tickets
    • 'Problems' tab
      • Create a new Problem for this ticket...   (***It already exists***)
    • 'Changes' tab
      • Create a new Change for this ticket...   (***It already exists***)
    • 'Project tasks'
      • Associate this ticket to the Task #x of Project #y...
      • Create a new Project Task into Project #n for this ticket...   (***The Project #n must exists***).
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this ticket...
  • Problems
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this problem...
  • Changes
    • 'Projects' tab
      • Create a new Project for this change...
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this change...
  • Projects
    • 'Knowledge base' tab
      • Create a new Knowledge Item for this project..


That is all. Thanks in advance and best regards,