- What is the Linked issues Custom Field?
- Setup Guide
- Field Contexts
- Display Modes
- Field Value and Search
- Automatic Cleanup
- Limitations
- Next Steps
What is the Linked issues Custom Field?
The app adds the custom field type Linked issues (“Custom field that displays a table of issues linked to the issue”). A field of this type shows the linked issues table on the issue view, wherever the field is placed: in the main column or in the Details section on the right - the issue layout of each issue type decides where.
The field is shown on the issue view only, not on create forms or the customer portal, and users cannot edit it.
Setup Guide
- Make sure the Custom Field module is on: Apps → Display Linked Issues settings → Module Settings.
- A Jira administrator creates a custom field of type Linked issues (Jira Administration → Issues → Custom Fields → Create custom field).
- In the field’s context settings, configure the table for that field context: link types or JQL, columns, limits and the other settings of a configuration.
- Add the field to the issue layouts where it should appear.
Field Contexts
Jira custom fields use contexts to define which projects and issue types the field applies to. Display Linked Issues leverages these contexts to provide different configurations per context.
This means you can show:
- One table for Bug issues in Project A
- A different table for Story issues in Project A
- Yet another table for all issues in Project B
Each context has its own independent configuration - link types or JQL, columns, limits and display conditions.
How Contexts Work
- When Jira displays the custom field, it determines which field context applies based on the current project and issue type
- Display Linked Issues looks up the configuration for that specific context
- The configured table of linked issues is displayed in the field
Note: If no configuration exists for a context, the field displays as empty.
Display Modes
Issue View (Read-Only)
On the issue view screen, the custom field displays the linked issues table as a read-only field value. It appears alongside other custom fields, in the main column or in the Details section.
Field Value and Search
For a configuration in Link types mode the field also has a value: the keys of the linked issues of the chosen link types, for example PROJ-3, PROJ-12, up to 255 characters (longer lists end with “…”). Only issues of the same project without an issue security level are included. The value can be used in JQL search and in issue lists.
Automatic Cleanup
Display Linked Issues automatically manages custom field configurations through an hourly scheduler that detects changes to fields and contexts.
What the Scheduler Detects
| Change | Action |
|---|---|
| Custom field deleted in Jira | Configuration is disabled |
| Field context removed | Associated configuration is disabled |
| Field context re-added | Configuration can be manually re-enabled |
How It Works
- The scheduler runs every hour
- It checks all custom field configurations against Jira’s current field and context data
- Orphaned configurations (where the field or context no longer exists) are marked as disabled
- Disabled configurations remain in the list and can be cleaned up manually or re-enabled if the field/context is restored
This prevents stale configurations from accumulating and ensures the system stays in sync with your Jira custom field setup.
Limitations
- Issue view only - the field is not shown on create forms, transition screens or the customer portal
- One configuration per context - Each field context has a single configuration (unlike panel modules where multiple configs can target the same module); a context without one shows nothing
- Field value - only in Link types mode, up to 255 characters, issues of the same project without an issue security level
Next Steps
- Modules - Overview of all display modules
- Configuration Basics - Create and manage configurations
- Templates - Dynamic content with template syntax
- FAQ - Custom field troubleshooting

