This saves the state of hosts and items tables (search input,
ordering, paging position) so that it can be restored when the user
reloads a page.

See https://datatables.net/examples/basic_init/state_save.html

JIRA INFRA-608 #action In Progress

JIRA INFRA-575 #action In Progress

The buttons should only be created if the items_table exists

JIRA INFRA-584

Retrieving all items from the database takes some time.
The task is thus handled by the RQ worker.
We use ajax to periodically monitor the status of the job
and redirect to the file when ready.
A progress bar is displayed to let the user see the progress.

The mechanism put in place could be re-used for other use cases.

JIRA INFRA-545 #action In Progress

Allow to use a scanner configured as keyboard to register items
via the web UI.
1. The attributes should be selected manually
2. Focus set manually on ICS id
3. Scan an ICS id -> prefix removed and focus set to serial number
4. Scan serial number
5. Click on submit
6. Focus set automatically on ICS id
7. Repeat from 3

Allow to keep track of batches of small parts.

Sorting on manufacturer/model/location/status requires
a join which removes the row with empty field.
Disable it until we find a way to sort properly including null values.

When there are more than a 1000 items in the table, retrieving and
displaying all items takes about 7 seconds.
This is every time we refresh the items page, which is too slow.

Column not visible but searchable.
Allow to search comments and TAG number for items imported from JIRA.

See https://github.com/showdownjs/showdown/wiki/Extensions

Allow to scan a label to enter an ICS id via the web interface

text is really generic and could conflict with another variable.
body is often used for comments.

Scroll up to ensure the from input is not hidden below the navbar.

See https://github.com/twbs/bootstrap/issues/1768

Rendering done client side using Showdown: http://showdownjs.com
Live preview is shown below the form.
Only raw text is saved in the database (no HTML).

Note that no XSS filtering is done!
See https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)

- Main blueprint used to declare custom views for all blueprints.
(keep inventory blueprint cleaner)
- Add url_prefix to each blueprint