Field Behaviours for Jira Home

Field Behaviours for Jira makes Jira's Create dialog and issue view adapt to whoever fills them in. Make fields required, read-only or hidden, rename them, fill in values and limit the options people can pick, based on the project, the issue type, the current user or another field. No code needed, and Jira expressions plus your own APIs are there when you need more.

Field Behaviours product tour
Field Behaviours in 45 seconds. Turn on the sound for the narration.

What you can do

You want to…

Use

You want to…

Use

Make a field required, read-only or hidden, for everyone or only for some people

Set Required, Set Read-Only or Hide with a condition

Give a field a different name or help text in one project

Set Name and Set Description

Fill in a value for people, such as the project lead as approver

Set Value, with a fixed value or a Jira expression

Show only some options of a select field, Priority or Issue Type to a team

Configure Option Visibility

Change a field as soon as someone changes another one

The On Change trigger, see Creating a Behaviour

Use data from your own system, such as cost centers from an ERP

Data sources and external parameters

Offer different options for each issue type in the same project

Multi Context Select fields

Change the customer portal request form and the agent views in service projects

Jira Service Management

The same Create form for the Support group and the Finance group
One Create form, different rules: Reporter is read-only for Support, Approver is required and Budget is visible for Finance.
Configure Option Visibility hides Highest and Lowest for the Developers role
Configure Option Visibility: developers see only High, Medium and Low.
Adding a data source and testing the connection
Connect a REST API once, test it, then use its data in any behaviour.

New here?

Start with Getting Started. It takes you from install to your first working behaviour in about ten minutes: the Approver field becomes required as soon as someone raises the priority.

Browse the documentation

Section

What is inside

Section

What is inside

Getting Started

Install the app, find its pages and build your first behaviour

User Guide

How behaviours work, then step by step: Creating a Behaviour, Operations, Basic Configuration, Advanced Configuration, Data Sources, Logs, Multi Context Select Fields and Use Cases and Examples

FAQ and Troubleshooting

Answers to common questions, what to check when a behaviour doesn't run, and what each error message means

Security, Data and Limits

Where the app runs, what it stores, what leaves your site, permissions and every limit in one table

Release Notes

What changed, newest first

Jira now says work item, space and work type where it used to say issue, project and issue type. The app's screens and this documentation still use the older words. They mean the same thing.

Get help

All pages