Jira Cloud Default Values vs Placeholder Text

In Jira Cloud, you should use default values when you want a field to be pre-filled with a specific value that the user can change, and placeholder text when you want to show a hint or example inside an empty field. Default values are set per project and apply to all new issues, while placeholder text is purely visual guidance that disappears as soon as the user starts typing. This article explains the difference, when to use each, and how to set them up.

Background: What Are Default Values and Placeholder Text?

Jira Cloud gives you two ways to guide users when they create an issue: default values and placeholder text. They look similar at first glance, but they behave very differently.

• Default value: A value that is automatically inserted into a field when a new issue is created. The user sees the value and can edit or delete it. It is stored as part of the issue data.
• Placeholder text: A greyed-out hint that appears inside an empty field. It disappears as soon as the user clicks or types. It is never stored or submitted.

Both are configured in the project’s fields settings, but they serve different purposes. Default values reduce repetitive typing; placeholder text clarifies what format or content is expected.

How Default Values Work in Jira Cloud

Default values are set at the project level, not globally. You can set a default value for most custom fields and for some system fields, such as Priority, Components, or Fix Version.

To set a default value:

1. Go to Project settings > Fields.
2. Find the field you want to edit and click the … (ellipsis) menu.
3. Select Set default value.
4. Choose the value from the dropdown or enter it.
5. Save.

When a user creates a new issue in that project, the field is pre-filled with the default. The user can change it, and the changed value is what gets saved. If the user deletes the value and leaves the field blank, the issue can still be created (unless the field is required).

Important: Default values apply only to new issues. Existing issues are not updated. Also, default values are not available for all field types—for example, you cannot set a default for a text field in the standard Jira Cloud interface, only for select lists, multi-selects, radio buttons, checkboxes, and some others.

How Placeholder Text Works in Jira Cloud

Placeholder text is a relatively new feature in Jira Cloud (added around 2022). It is available for text fields, text areas, and number fields. You set it in the same Project settings > Fields area.

To set placeholder text:

1. Go to Project settings > Fields.
2. Find the text field you want to edit.
3. Click the … menu and select Set placeholder text.
4. Enter the hint text (e.g., “Enter the customer’s email”).
5. Save.

The placeholder appears in grey inside the field when it is empty. Once the user clicks and starts typing, the placeholder disappears. If the user clears the field, the placeholder reappears.

Placeholder text is never saved. It is purely a visual aid. It also does not affect validation—if a field is required and empty, the placeholder does not count as a value.

Which Should You Use? A Practical Guide

Choose default values when you want to reduce data entry for a common choice. For example, if most bugs in your project are of severity “Medium”, set the Priority field default to “Medium”. Users can still change it to “High” when needed.

Choose placeholder text when you want to tell the user what to enter, but you do not want to pre-fill anything. For example, a description field might show “Describe the steps to reproduce the bug, including the expected and actual result.”

Here is a quick rule of thumb:

• Use a default value if the field is a dropdown, radio button, or checkbox, and one option is clearly the most common.
• Use placeholder text if the field is free text and you need to provide an example or format hint.
• Do not use a default value for a text field that expects a unique answer (like a ticket ID) because it will confuse users.
• Do not use placeholder text as a substitute for a field description—placeholders are not visible once the user starts typing, so important instructions should go in the field description.

Common Problems and Misconceptions

One common misconception is that placeholder text can be used to set a value that gets submitted. It cannot. If you need a value to be present in the issue, you must use a default value or a field description.

Another issue: default values are project-specific. If you have multiple projects, you must set the default in each project. There is no global default in Jira Cloud (as of this writing).

Also, default values do not work on the “Create” screen if the field is hidden. If you want a default value to appear, the field must be on the create screen.

Finally, placeholder text is not supported on all field types. It works on text fields, text areas, and number fields, but not on select lists or checkboxes. For those, you would use a default value or a description.

Comparison: Default Value vs Placeholder Text

Aspect	Default Value	Placeholder Text
Purpose	Pre-fill a value	Show a hint
Stored in issue	Yes, if not changed	No, never
Visible after typing	Yes, as the value	No, disappears
Field types	Select, multi-select, radio, checkbox, some system fields	Text, text area, number
Project-level	Yes	Yes
Can be required	Yes, but user can delete	No, not a value

Best Practices for Jira Cloud Fields

To get the most out of these features, follow these guidelines:

• Use default values for fields with a clear majority option (e.g., Priority = Medium, Component = Frontend).
• Use placeholder text for fields that need a format example (e.g., “DD/MM/YYYY” for a date field, or “Enter the URL of the failing page”).
• Keep placeholder text short—under 50 characters—so it does not get cut off.
• Combine both: set a default value for a select field and a placeholder for a related text field.
• Test on a sample project before rolling out to the whole team.
• Review your fields periodically—defaults can become outdated as workflows change.

Frequently Asked Questions

Can I set a default value for a text field in Jira Cloud? No, not in the standard interface. Default values are available only for select, multi-select, radio, checkbox, and some system fields like Priority or Fix Version. For text fields, use placeholder text or a field description.

Does placeholder text affect issue creation? No. Placeholder text is purely visual. If a field is required and the user leaves it empty, the issue will not be created, even if placeholder text is present.

Can I use placeholder text on a dropdown field? No. Placeholder text is only available for text, text area, and number fields. For dropdowns, use a default value or a field description.

Will changing a default value affect existing issues? No. Default values only apply to new issues created after the change. Existing issues keep their current values.

How do I remove a default value? Go to Project settings > Fields, click the ellipsis on the field, and select “Unset default value”. The field will then be empty on new issues.

Can I set a default value for a user picker field? Yes, you can set a default user for a user picker field, but it must be a single user. It will pre-fill with that user on new issues.

Related

• Convert AVI to MPEG: How-To & Best Ways
• 3D Printer Filament Moisture Storage Tricks
• Swift Programming 101: Power Extensions