Is it planned to list generic assets in tickets in the final GLPI 11?
Closed this issue · 15 comments
Code of Conduct
- I agree to follow this project's Code of Conduct
Contribution description
Good evening, everyone!
I just want to raise an issue here related to assets: as in version 10, I noticed that in version 11 there is also only the option to link native system assets, except for generic assets.
Now that generic assets are being entered as native, is there any plan to include the feature of linking them in calls as well?
When I say link, I mean like when you associate a computer with a ticket, for example, and then you can also associate that same computer through the form, as well as phones, printers, etc., everything except assets that are created by generic assets.
Version in question: GLPI 11 RC5
Thank you for your attention!
Translated with DeepL.com (free version)
You can add the custom assets as being allowed to be linked to tickets/changes/problems per-profile like other assets, but unlike most native assets they are not allowed to be linked by default. You can do this from the Profiles tab of the custom asset definition form or from individual profile forms.
@cconard96 True, but I noticed something that could be seen as an improvement: even with that button marked “all items” within the profile > assistance, when you create a new item, it does not automatically consider that new item, so you end up having to go there and activate the new object in the profile > assistance to be able to associate it. This ends up going unnoticed because it is a very subtle permission.
The "All" button works the same for all dropdowns that accept multiple values. It adds all current options to the selection rather than representing all current and future options.
Ok @cconard96 You can test in GLPI 11 rc5 the association of assets in the ticket destination via the form?
I tried to open a ticket here in the native way and the asset associates normally, but through the form, both a computer and a generic asset, for example, do not associate. I also noticed that when you create the ‘specific asset’ association type, you choose one and below it creates an empty field.
Path to replicate: within the form > destinations > Associated assets
Expected behavior: open call with asset related to the issue or specifically as marked in the form properties.
Hello Lucas, can you share an export of your form here so we can try on our side?
There's an "export" button under the action menu (top right of the page).
I think this might be related to this fix : #21053
It should be OK now in the 11.0.0 release, can you please retry?
@AdrienClairembault From my testing, it remains the same. The generic asset does not appear in the form destination, and even if I create a generic asset question and associate that item, and even associate the question with the destination, it does not appear in the call as an associated item.
Testei novamente no glpi 11.0.1, mas ainda nao consigo associar ativos genericos direto no formulario
Could you please write in english only?
Hello @lucaslevi-consultor-glpi,
I've tried again on my side and it seems OK.
Here is my very simple form:
I didn't modify anything else on the ticket besides adding a question.
Then, I select an item when filling my form:
And it is set correctly in the created ticket:
Note that it will only work if you allow your custom itemtype to be associated with tickets (this is done in the profiles configuration, it must be set for all the possible profiles that will be creating ticket with this form):
Upon closer inspection, I noticed that within the created asset > capacity there is no option to mark ‘tickets’. I don't know if this is related.
This is on purpose, since it already needs to be enabled for each profiles there is no need for a specific capacity.
I created this Owa5x asset, but I can't select it. Is this a bug related to this?
It seems unrelated, you should probably open a dedicated issue with as much details as possible.
@AdrienClairembault It worked. I had forgotten that detail, but last time it really wasn't listing even though I had checked it in my profile. Now that part seems to be OK.
Great, I'll let you reopen this issue if it happens again.

