How to list all screens associated with the "Create Issue" Operation:

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This article can be useful when you need to compile a list of all screens associated with the "Create Issue" operation.

Environment

All on-prem versions (Data Center and Server) of Jira Software and Jira Service Management.

Solution

You may accomplish this through a database query directly in Jira's DB.

Note : query the DB directly through a DB client — not through any app within Jira, as these apps often apply row count limitations and may not report the full picture.

1 2 3 4 SELECT DISTINCT e.id, e.fieldscreen as fieldscreenid, f.name as fieldscreenname FROM fieldscreenschemeitem, fieldscreen f join fieldscreenschemeitem e on e.fieldscreen = f.id where e.operation IS NULL or e.operation = 0;

We're basically joining the info from the fieldscreenschemeitem table to the fieldscreen table. The "fieldscreenschemeitem.operation" = NULL or 0 are both associated with the creation issue operation.

Example output

1 2 3 4 5 6 7 8 9 10 id | fieldscreenid | fieldscreenname -------+---------------+----------------------------------------------- 10000 | 1 | Default Screen 10100 | 10000 | SCRUM: Scrum Default Issue Screen 10101 | 10001 | SCRUM: Scrum Bug Screen 10102 | 10002 | KANBAN: Kanban Default Issue Screen 10103 | 10003 | KANBAN: Kanban Bug Screen 10200 | 10100 | FP: Software Development Default Issue Screen 10201 | 10101 | FP: Software Development Bug Screen (7 rows)

Updated on March 20, 2025

Still need help?

The Atlassian Community is here for you.