Summary

In some scenarios, it may be necessary for a field to remain uneditable in the issue view while still allowing it to be populated during issue creation. This can be achieved by configuring separate screens for the Create, View, and Edit operations. The field to be made uneditable should be included only on the Create and View screens but excluded from the Edit screen.

Environment

Jira Cloud

Solution

This is an illustration of the solution:

Project Configuration:

• Project: Editable Field
• Field: EditNonEdit

Screens Created:

1. EF Create Screen: Includes the EditNonEdit field.
2. EF Edit Screen: Excludes the EditNonEdit field.
3. EF View Screen: Includes the EditNonEdit field.

Step-by-Step Implementation

1. Create Screens for Each Operation

Separate screens must be created for the Create, Edit, and View operations to control where the field is displayed and where it remains uneditable.

Steps:

• Navigate to Settings > Issues > Screens.
• Click Add Screen.
• Provide a name for the screen (e.g., "EF Create Screen") and add the necessary fields, including the field that needs to be uneditable (e.g., EditNonEdit).
• Repeat the process for the Edit and View screens. For the EF Edit Screen, ensure the EditNonEdit field is excluded so that it cannot be edited after issue creation.

2. Create a Screen Scheme

A Screen Scheme connects the created screens to their respective issue operations (Create, Edit, and View).

Steps:

• Navigate to Settings > Issues > Screen Schemes.
• Select Add Screen Scheme.
• Name the scheme (e.g., "EF Screen Scheme") and assign the default screen.
• Open the new Screen Scheme and associate the issue operations (Create, Edit, View) with the corresponding screens.

3. Associate the Screen Scheme with an Issue Type

To apply this configuration to the necessary issue types, the Screen Scheme must be associated with the relevant issue type screen scheme.

Steps:

• Navigate to Settings > Issues > Issue Type Screen Schemes.
• Either select an existing scheme or create a new one.
• Open the chosen Issue Type Screen Scheme and link it to the EF Screen Scheme created earlier for the relevant issue types (e.g., Bugs, Tasks, etc.).

Outcome:

Creating an Issue: The "EditNonEdit" field will appear as expected for populating the value.

Viewing/Editing an Issue: The field will be visible but non-editable.