Skip to content

[Feature Request]: Customizable QR Code Content for Asset Labels #15107

@NebelKreis

Description

@NebelKreis

Is your feature request related to a problem? Please describe.

Currently, the QR codes generated for asset labels in Snipe-IT contain the Snipe-IT link to the asset, which includes a sequentially generated ID. While this is useful, it would be more beneficial if users could choose what information is embedded in the QR code. For example, including the asset tag, model number, manufacturer, etc., would allow for more flexibility and utility in different use cases.

Describe the solution you'd like

I propose adding a feature that allows users to customize the content of the QR codes generated for asset labels. This feature should provide options to include various pieces of asset information such as:

1.	Asset Tag
2.	Model Number
3.	Manufacturer
4.	Serial Number
5.	Custom Fields

The user interface for generating asset labels should include a section where users can select which pieces of information they want to be included in the QR code. This could be implemented using checkboxes or a similar selection mechanism.

Describe alternatives you've considered

Currently, the QR code link in Snipe-IT uses a sequentially generated ID for each asset. As an alternative, it could be beneficial to provide an option to use the asset tag instead of the sequential ID, since the asset tag is unique and typically remains constant unless changed under special circumstances.

Additional context

This feature would significantly enhance the flexibility and functionality of the QR codes on asset labels. Different organizations have different needs, and being able to customize QR code content would allow them to tailor the labels to their specific requirements. For example, some organizations might prioritize quick access to the asset tag and serial number, while others might need the model number and manufacturer information readily available.

Metadata

Metadata

Assignees

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions