Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Computer information rules - no entity used #2416

Closed
mohierf opened this Issue Jan 5, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mohierf
Copy link
Collaborator

mohierf commented Jan 5, 2018

Assigning a status information from a regex do not use any entity information. As such, Glpi will use -1 as entity id.

The result is that the newly created statuses are not editable from the Glpi Statuses view. See hereunder:

image

@mohierf

This comment has been minimized.

Copy link
Collaborator Author

mohierf commented Feb 1, 2018

The main problem with this bug is that the information collected for a computer are only available from the Root entity:
image

Whereas those information are collected for computers that are in a sub-entity !

@mohierf mohierf self-assigned this Feb 7, 2018

@mohierf

This comment has been minimized.

Copy link
Collaborator Author

mohierf commented Feb 7, 2018

Forget the 2nd comment ... indeed it seems related to the 1st one but it is another problem.

For the real problem it is because the Statuses managed by Glpi are now concerned with entities and the FI plugin do not manage entities for all the items that may create a status. Fixed with @ddurieux today, I will submit a PR soon for this.

@mohierf mohierf added the bug label Feb 7, 2018

mohierf added a commit to mohierf/fusioninventory-for-glpi that referenced this issue Feb 7, 2018

mohierf added a commit to mohierf/fusioninventory-for-glpi that referenced this issue Feb 8, 2018

@ddurieux ddurieux added this to the 9.2+2.0 milestone Apr 2, 2018

ddurieux added a commit that referenced this issue Apr 2, 2018

@ddurieux ddurieux closed this in 4e18880 Apr 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.