> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/rules/use-name.md).

# Use name: change a Jira field's label based on conditions

Change a Jira field's name (its label) based on the work type, another field's value, or the user's group, role, or identity. No scripting.

Field Rules can override a Jira field's name - the label shown with the field on the screen - based on conditions, so the same field reads differently depending on context. Relabel a generic field to match the work type being created, clarify what a field means for a specific request, or adapt the label by user, group, role, or another field's value, with no code.

***

## How to set it up

1. Open the **UI Modification** for the context you want to control (space, work type, and view).
2. Add a **Use name** rule and choose the field under **Field name**.
3. Enter the **Display name** text to show (required, up to 255 characters, plain text).
4. Add **preconditions** - field values and/or user identity - that determine when the custom name appears. When conditions are not met, the field's original name is restored automatically.
5. Save. The name updates in real time as values on the screen change, no reload required.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-cb0673b4f875887a15b962fb41e574d974a33c26%2Fuse-name-rule-config.png?alt=media" alt="Configuring a Use name rule that renames the Reference field to Serial number when Category is Hardware"><figcaption><p>Renaming the Reference field to "Serial number" when Category is "Hardware".</p></figcaption></figure>

| Option            | Description                                                                                                                                   |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field name**    | The field whose name will be overridden.                                                                                                      |
| **Display name**  | The text to display as the field's label. Required, maximum 255 characters, plain text.                                                       |
| **Preconditions** | Optional field and/or user conditions. When conditions are met the custom name is shown; when they are not met the original name is restored. |

***

## How it works

When the screen loads and the configured preconditions pass, the rule replaces the field's label with the configured text. If the preconditions later become false (for example, because the user changes a watched field), the label reverts to its original value automatically. This happens in real time as values on the screen change, without a page reload.

{% hint style="info" %}
Use name changes only the label shown on the selected screen. It does not rename the custom field itself, so JQL, filters, boards, reports, notifications, and other screens keep the field's original name.
{% endhint %}

On the JSM portal this rule is the dynamic equivalent of a request type's **Display name** (set in its Request form settings). If both are configured for the same field, the Use name rule takes precedence.

The name is plain text only, wiki markup and rich text are not supported, and it is capped at 255 characters. Leading and trailing spaces are removed by Jira when the label is applied.

***

## Examples

**Relabel based on another field's value**\
A generic "Reference" text field is reused for several purposes. When a "Category" select is set to "Hardware", rename it to "Serial number". The label follows the user's choice, and reverts when the category changes.

**Clarify a field on a transition**\
When a "Reject" transition screen loads, rename the Resolution field to "Reason for rejection" so the choice is unambiguous at the moment it is made.

**Audience-specific labels**\
When the current user belongs to the "Support" group, rename a field to use internal terminology, while everyone else sees the standard label.

**Same portal label across several request types**\
On the JSM portal, a single UI Modification can cover several request types through its context, so one Use name rule gives a shared field the same customer-friendly label across all of them, instead of setting the Display name separately in every request type's Request form settings.

***

## When to use it

Reach for Use name whenever a field's meaning shifts with context and one fixed label would be wrong some of the time:

* **Reuse one field across work types** - give a shared field a label that matches what is being created, instead of maintaining a separate field per work type.
* **Pair it with another rule** - relabel a field you have [locked](https://docs.forgappify.com/field-rules/rules/lock-field.md) or [required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) so its new role is clear.
* **React to conditions, not just context** - vary the label by another field's value or by the user's group, role, or identity, and update it live as values on the screen change.

***

## Doing this without Field Rules

In native Jira a custom field has a single, global name. Renaming it in the custom field settings changes the label everywhere, in every space, work type, and view at once, so on the Create issue, Issue view, and Issue Transition screens there is no built-in way to show one field under different labels depending on context. The usual workaround is to create a separate custom field for each variation and place each on the relevant screens, which multiplies the fields to maintain and report on.

The JSM customer portal is the exception: each request type's Request form settings has a Display name that relabels the field on that form. It is a static setting, configured one request type at a time, and it does not react to what the customer enters. Giving the same label to several request types means repeating it in each request type's settings individually.

Use name replaces both with a per-context label: one field, relabeled by work type, user, group, role, or another field's value, and updating live as values on the screen change. On the portal, a single UI Modification can span several request types through its context, so one rule relabels the field across all of them. Varying a label by a field value or user, or updating it as values on the screen change, otherwise requires a UI Modifications app like Field Rules or a scripting app. Field Rules closes this gap with a no-code, visually configured rule, no developer required.

See [Field Rules vs native Jira](https://docs.forgappify.com/field-rules/jira-administrator/field-rules-vs-native-jira.md) for the full comparison across every rule.

***

## Supported fields

The JSM Agent views behave like their standard equivalents.

| Field type        | Global Issue Create | Issue View | Issue Transition | JSM Request Create |
| ----------------- | ------------------- | ---------- | ---------------- | ------------------ |
| Assignee          | Yes                 | Yes        | Yes              | No                 |
| Affects versions  | Yes                 | Yes        | Yes              | No                 |
| Cascading select  | Yes                 | Yes        | Yes              | Yes                |
| Checkboxes        | Yes                 | Yes        | Yes              | No                 |
| Components        | Yes                 | Yes        | No               | No                 |
| Date picker       | Yes                 | Yes        | Yes              | Yes                |
| Date time         | Yes                 | Yes        | Yes              | Yes                |
| Description       | Yes                 | Yes        | Yes              | Yes                |
| Due date          | Yes                 | No         | No               | Yes                |
| Fix versions      | Yes                 | Yes        | Yes              | No                 |
| Labels            | Yes                 | Yes        | Yes              | Yes                |
| Multi select      | Yes                 | Yes        | Yes              | Yes                |
| Multi user picker | Yes                 | Yes        | Yes              | No                 |
| Number            | Yes                 | Yes        | Yes              | Yes                |
| Original estimate | No                  | Yes        | Yes              | No                 |
| Paragraph         | Yes                 | Yes        | Yes              | Yes                |
| Parent            | Yes                 | Yes        | Yes              | No                 |
| People            | Yes                 | Yes        | No               | No                 |
| Priority          | Yes                 | Yes        | Yes              | Yes                |
| Project picker    | Yes                 | Yes        | Yes              | No                 |
| Radio buttons     | Yes                 | Yes        | Yes              | No                 |
| Reporter          | Yes                 | Yes        | Yes              | No                 |
| Resolution        | No                  | No         | Yes              | No                 |
| Select            | Yes                 | Yes        | Yes              | Yes                |
| Summary           | Yes                 | No         | Yes              | Yes                |
| Target end        | Yes                 | No         | No               | No                 |
| Target start      | Yes                 | No         | No               | No                 |
| Text field        | Yes                 | Yes        | Yes              | Yes                |
| URL               | Yes                 | Yes        | Yes              | No                 |
| User picker       | Yes                 | Yes        | Yes              | Yes                |

***

## Limitations

* **Issue Type** does not support this rule on any view.
* The name is **required** and cannot be empty.
* The name is **plain text only**, wiki markup and rich text are not rendered.
* Leading and trailing spaces are trimmed when the label is applied.
* The name is capped at **255 characters**.

***

## Related rules

* [Use description](https://docs.forgappify.com/field-rules/rules/use-description.md) - change a field's hint text based on conditions.
* [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md) - explain why a field is locked.
* [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) - explain why a field is required.
