---
title: "Can item types or Source IDs be explicitly labeled (e.g., “SYSREQ” for System Requirements, “UNREQ” for User Needs Requirements) instead of the generic “REQ” format?"
description: "Yes, Ketryx allows for customization of item types and their labels. There are a couple different ways that this can be achieved through the advanced settings. 1\\. Create a custom item type Ketryx provides the ability to define custom item types with unique labels."
category: "Frequently Asked Questions"
section: "Software Release Process"
keywords: ["req", "source ids", "generic", "user needs", "explicitly", "labels", "settings documentation", "custom types"]
source_url: "https://support.ketryx.com/hc/en-us/articles/34416142464141-Can-item-types-or-Source-IDs-be-explicitly-labeled-e-g-SYSREQ-for-System-Requirements-UNREQ-for-User-Needs-Requirements-instead-of-the-generic-REQ-format"
last_reviewed: 2026-06-11
---

# Can item types or Source IDs be explicitly labeled (e.g., “SYSREQ” for System Requirements, “UNREQ” for User Needs Requirements) instead of the generic “REQ” format?

> **In short:** Yes, Ketryx allows for customization of item types and their labels. There are a couple different ways that this can be achieved through the advanced settings. 1\. Create a custom item type Ketryx provides the ability to define custom item types with unique labels.

Yes, Ketryx allows for customization of item types and their labels. There are a couple different ways that this can be achieved through the advanced settings.

## 1\. Create a custom item type

Ketryx provides the ability to define custom item types with unique labels. Please note that this will create a new item type in Ketryx and in Jira.

For more details, refer to our **\[ [Advanced Settings Documentation](https://docs.ketryx.com/reference/advanced-settings#custom-item-types)\]** and **\[ [Custom Item Types Reference Guide](https://docs.ketryx.com/reference/custom-item-types)\]**.

You can configure custom item types with specific names and short names. For example:

\[\
\
{\
\
"lifecycle": "LONG_LIVED",\
\
"name": "System Requirement",\
\
"shortName": "SYSREQ"\
\
},\
\
{\
\
"lifecycle": "LONG_LIVED",\
\
"name": "Use Case Requirement",\
\
"shortName": "UNREQ"\
\
}\
\
\]

## 2\. Map the item type.

Existing item types can be mapped to the desired naming convention. See our **\[ [Advanced Settings Documentation](https://docs.ketryx.com/reference/advanced-settings#project-item-configuration)\].**

## 3\. Consider using document templating.

If you'd like the requirement type to be immediately apparent in your documentation, consider using [document templating](https://docs.ketryx.com/reference/document-templating) to have the requirement type show up in close proximity to the issue ID.

## Related articles

- [How can I add my own types of requirements in the Ketryx Requirement Type field?](how-can-i-add-my-own-types-of-requirements-in-the-ketryx-requirement-type-field.md)
- [How can I make a custom read-only field with a default value appear only for a specific item type in Ketryx?](how-can-i-make-a-custom-read-only-field-with-a-default-value-appear-only-for-a.md)
- [How does Ketryx ensure that unique IDs are created for git-based configuration items?](how-does-ketryx-ensure-that-unique-ids-are-created-for-git-based-configuration.md)
- [How do I create a custom item type in Ketryx?](how-do-i-create-a-custom-item-type-in-ketryx.md)
- [How do I import data into my Jira project?](how-do-i-import-data-into-my-jira-project.md)