I think it should go further.
GLPI should allow the creation of internal links to the resources it manages just like Redmine does for example (https://redmine.org/projects/redmine/wiki/RedmineTextFormattingMarkdown).
In other words, it is possible to create a mark for articles in the knowledge base, tickets, inventoried goods, documents, etc.
Each managed object should have a mark and a number specification (internal code) or description, and should automatically generate the link.
Example:
#kb:1
#kb:"title of knowledge base article"
#prj:1
#prj:"project name"
#prj:1#tsk:12
#prj:1#tsk:"task title"
All with the intention of not referring to a complete URL, since they are not external resources but internal resources.
Regards.
Customer support service by UserEcho
I think it should go further.
GLPI should allow the creation of internal links to the resources it manages just like Redmine does for example (https://redmine.org/projects/redmine/wiki/RedmineTextFormattingMarkdown).
In other words, it is possible to create a mark for articles in the knowledge base, tickets, inventoried goods, documents, etc.
Each managed object should have a mark and a number specification (internal code) or description, and should automatically generate the link.
Example:
#kb:1
to indicate article 1 of the knowledge base#kb:"title of knowledge base article"
#prj:1
or#prj:"project name"
to indicate projects#prj:1#tsk:12
or#prj:1#tsk:"task title"
to indicate a task of a projectAll with the intention of not referring to a complete URL, since they are not external resources but internal resources.
Regards.