Feature tour
Show or Hide fields based on other field values
Dynamically show or hide fields depending on what’s selected in another field to keep processes relevant and streamlined.
For example:
Hide specific fields based on selected Components
Show fields only for specific issue types
Show fields only for issues with higher Story Points
Make fields mandatory to keep data accurate
Set fields as required only when necessary. Specific fields can be made required based on the values of other fields, guaranteeing data completeness without increasing the complexity of your Jira field configuration schemes.
For example:
Set Priority as mandatory for production bugs but optional for development bugs
<other example goes here>
<third example goes here
Auto-fill fields for improved processes
Auto-populate field values to improve data quality and streamline data entry. When working with nearly any aspect of an issue, you can automatically fill or update fields based on your choices.
For example:
Pre-filling the Summary or Description fields with editable templates
Setting standard or custom fields when creating issues of a specific issue type
Update fields when other fields are changed
Make fields read-only to control access
Restrict fields to view-only mode for certain users, to allow visibility of important details without unauthorized changes. Keep fields visible for all users without risking inaccurate information.
For example:
Make some fields editable only by the Project Lead or Product Owner
Ensure only Developers can update specific fields
You are viewing the documentation for Jira Cloud.