/
Editable Barcode/QR Code

Editable Barcode/QR Code

Overview

The Editable Barcode/QR Code custom field allows users to directly enter text, numbers, or ID information into a Jira issue and instantly convert that data into a scannable barcode. The field's value can be updated at any time, and the generated barcode can be printed for physical use.

By default, this field automatically generates a QR Code (2D) for each issue. If you prefer, you can change this setting to the one-dimensional (1D) Code 128 from the field's configuration page.

Configuring an Editable Barcode/QR Code

To set up an Editable Barcode, navigate to its configuration page.

From there, choose a barcode type using the dropdown menu and click Save.

editable-issue-screen.png

Issue Screen After Configuring an Editable Barcode/QR Code

editable-barcode-edit.png
editable-barcode-view.png

NOTES

Text length directly affects a barcode's scannability. To ensure reliability with longer text, we recommend choosing the QR code option.

Code 128 only supports ASCII characters. If the text contains non-ASCII characters (e.g., ş, ğ, ö), a barcode cannot be generated with this option. In this case, you must select the QR code option, as it supports all character sets.

EXAMPLE USE CASES

1.Linking Physical Devices to Jira Issues

This use case is designed to link a Jira issue to any physical device or piece of hardware. A unique identifier for the device, such as a serial number or an asset code, is entered into the field to generate a barcode. When affixed to the device, this barcode allows any team member to scan it for instant access to the correct Jira record. This method streamlines processes like inventory management, new device setup, maintenance, and fault tracking, ensuring an error-free data flow.

2.Quick Access to External Support Tickets

This use case links a development task in Jira to the original customer ticket in an external support system (e.g., Zendesk). The support team generates a barcode that provides instant access to this information by entering the original ticket number into the Jira issue. This allows developers to solve problems more efficiently by accessing the full history and details of the customer complaint with a single scan.