Added #15107: Customizable 2D Barcode Content for Asset Labels

[NebelKreis]

Description

This PR introduces a new feature that allows users to customize the content of the 2D barcodes generated for asset labels in Snipe-IT. Currently, the barcodes contain only the Snipe-IT link to the asset, which includes a sequentially generated ID or the asset tag. While this functionality serves its purpose, it limits the usability of the barcodes in various operational contexts.

To enhance this feature, the following changes were made:

• Added options for users to include the following pieces of asset information in the 2D barcode:

  • Asset Tag
  • Serial Number

• The user interface for selecting the 2D barcode target now includes 2 more options, now allowing users to select whether they want to include the asset tag or the serial number in the 2D barcode.

Note: This implementation serves as an initial solution. Future enhancements will include options to add more data fields and the ability to arrange the order of the displayed information in the 2D barcode. These improvements aim to provide greater flexibility and meet user requirements more effectively.

Fixes Issue: #15107

By allowing for customizable barcode content, this change enhances the overall functionality of the asset labels. Users can now quickly access critical information such as the asset tag and serial number directly from the barcode, increasing efficiency in asset management processes.

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Manual Testing: The new feature was manually tested to ensure that the customization options for the 2D barcode content are functioning correctly. This included verifying that the selected asset tag and serial number appear accurately in the generated barcodes.

• Unit Tests: New unit tests have been added to confirm that the customization functionality works as intended. All existing tests were run to ensure that no regressions were introduced by this feature.

Test Configuration:

• PHP version: 8.1.2
• MySQL version: 8.0.39
• Webserver version: Apache 2.4.52
• OS version: Ubuntu 24.04

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my feature works
• New and existing unit tests pass locally with my changes

[what-the-diff]

PR Summary

• Enhancement of Barcode Target Types
  In the Label.php file, new options - plain_asset_tag and plain_serial_number have been introduced to augment barcode target types.

• Code Consistency Improvement
  The switch statement in the Label.php file has been reformatted with line breaks, enhancing code readability and maintaining consistency.

• Addition of More User Choices
  In the labels.blade.php file, the select dropdown menu has been amplified to host new options for plain_asset_tag and plain_serial_number, enhancing user flexibility.

• Improved Array Alignment
  The arrangement of array elements in the labels.blade.php file has been modified for better readability and easier maintainability.

[snipe]

This seems like the same (or similar) to #15721 no?

[NebelKreis]

Yes, but I have also included the Serial Number as part of the customizable content.

Additionally, I am working on implementing logic that better separates links and data within the UI.
This will allow users to select and arrange multiple data points to be displayed in the barcode, providing more flexibility and control over the information shown.

[snipe]

I feel like maybe before opening a new PR, it might be more courteous to participate on the original PR that has been in progress for weeks to see if it could be a bit more collaborative between you and @Godmartinz who has been working on it. Now I'm supposed to choose between the two, which is not ideal.

[Godmartinz]

This works, on the select list we would like it if you could distinguish URL from VALUE like so:

Good stuff though 👍

[NebelKreis]

Thank you for the feedback!
I’ve adjusted the select list to clearly distinguish URLs from direct asset data. The first two options are now labeled with URL: to indicate they link to resources, while Data: prefixes the remaining options to identify direct asset values. Let me know if there are any further adjustments you’d like to see!

[snipe]

Looks like we have some failing tests here though.

[NebelKreis]

I’m not exactly sure why the tests failed, and I am unable to replicate the errors. Sending any type of emails works as expected, and they are being sent and received without any errors. I tested this on version 7.0.13 and now also on 7.1.14, both on Docker.

[snipe]

Hrm, can you try merging/rebasing down from current develop? Maybe that will shed some more light.

[NebelKreis]

At least it's a different error now, so I think it wasn't an issue with my code. I'll revert the rebase after review to clean up this mess.

[NebelKreis]

Looks like everything is passing now after the rebase! Let me know if there’s anything else that needs attention. Would be great to get this merged soon.

[Godmartinz]

Looks good @snipe

Thanks @NebelKreis 👍

[NebelKreis]

@snipe Just wanted to check in and see if there’s any update on when this PR might be merged. Let me know if there’s anything else I can do!

[snipe]

@NebelKreis looks like we have some conflicts that need to be resolved

[NebelKreis]

@snipe The conflicts have been resolved and everything should be good now.