Skip to content

Dealing with orders that contain multiple owners #71

Description

@driket

Context

Most of the time, there are different assets owners within a single order.
Thus, the delivery operator needs to keep track of the items ownerships.

Extra features development

2 years ago, I’ve modified the plugin to include 3 extra fields for each item in an order :

  • “Owner” & “Owner group”. They are automatically sent to inventory items during asset generation.
  • “Comment” is a free field allowing to help the delivery operator to know exactly what the item is. Can replace "Owner field" if user is not created yet.

screen_shot_2016-10-10_at_10_51_25

Feedback

Pros:

  • Delivery technician doesn’t have to open extra document to find out which assets belongs to which user
  • Auto-fills during delivery process seems to be less error prone

Cons:

  • Sometimes, the user doesn’t exist in GLPI/LDAP yet when the order is created. Then it’s not possible to process the automatic filling of user’s field in GLPI inventory. The "comment" field is then used as a workaround.

Sharing the modification

While this local modification has been appreciated in-house, I would like to know:

  • If this feature worth sharing in a pull request?
  • Does this feature break the purpose of the plugin / GLPI / ITIL?
  • What would be the common alternatives?

A lighter alternative

To just add one “Comment” field (string) for order items.

screen_shot_2016-10-10_at_16_37_44

Pros:

  • More general multi-purpose approach.
  • Allow delivery operator to keep track of items ownership within GLPI (without additional documents)
  • Help delivery operator to know exactly what the item is

Cons:

  • Delivery operator has to fill manually ownership field in inventory

Regards,

Cédric.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions