Hold the request makes the user hangs there waiting for response.

See merge request !533

See merge request !531

   This is a failover approach to prevent the user loose its value if it is not complaint with the field

See merge request !532

See merge request !524

  Do not browse whole related instance trees,  Only display directly related objects do keep more direct approach.

   This feature was merged into viewTickets, but we split into a second tab

   This uses catalog to fetch both Upgrades and Tickets, which is not good idea, since it has bad performance and use 2 listboxes works way better (since the columns differ).

   Script was removed since it had bad peformance

See merge request !530

See merge request !528

See merge request !526

See merge request !527

    if uid is empty it returns whole catalog

See merge request !529

   In short, use PUT rather them GET to request instance

    Use response from putAttachment to get the relative URL

   Call catalog on the uids for compute properly the list of objects to list (pagination + sort).

    Remarrk: This change isn't ideal and introduce an extra catalog call, but this only adds few microseconds (>10ms) to the return.

   - Fixup current Organisation on Compute Node UI (missing field)
   - Extend the query to fetch as much project and organisations as possible
   - Sort alphabetically, since it is more user_friendly
   - Keep single field (not current/Future) for each project, and pre-select the default

   - Fixup current Organisation on Compute Node UI (missing field)
   - Extend the query to fetch as much project and organisations as possible
   - Sort alphabetically, since it is more user_friendly
   - Keep single field (not current/Future) for each project, and pre-select the default

   This was prevent request form to restrict the software type to the proper one.

See merge request !525