...
The Object Dependencies report shows you where objects are used or referenced by other configuration objects in your instance. When analyzing your instance, you may need to know:
if the custom field field Technology is is used in any workflow.
the relation between a custom field and a project.
where a group is referenced, including role members, permissions, issue security schemes, workflows, etc.
...
Target instance: Following an import, you can run the report to see a mapping of instance dependencies and help you identify where changes are required if you encountered any errors.
Usage
To generate an Object Dependencies report,
...
select Manage Apps
...
from the Jira Administration
...
menu, then
...
select Object Dependencies Report
...
under Project Configurator
...
in the left sidebar.
...
Click Launch in the Object Dependencies Report
...
screen. The analyzed objects are displayed on the left of the report and grouped into tab links according to their type for easier navigation.
Click an object type link to display the tab for the corresponding objects, e.g. Workflow. The objects with dependencies are then displayed on the right side of the report. Any dependencies are displayed as links allowing you to easily navigate and track chains of interdependencies, and help you make informed decisions about your migration tasks. When a referencing object appears more than once, that object contains more than one reference to the used object.
In the example below, Workflow, PROJ987: Project Management Workflow, is used by Workflow Scheme Scheme PROJ987: Project Management Workflow Scheme, which is used by Project Project PROJ987.
 |
.png?version=2&modificationDate=1716287720533&cacheVersion=1&api=v2&width=851)
.png?version=2&modificationDate=1716287720533&cacheVersion=1&api=v2&width=448) |
Limitations
Inactive objects (those that are not used by any project, for example, inactive workflows or workflow schemes) are ignored. They will not be considered as objects that use or are being used by other objects.
Projects are never shown as used by other objects. This is not true in all cases in Jira, but in most practical cases it is convenient to treat projects as the roots of your configuration, i.e. the objects where one can start looking for the rest of configuration objects that are being used.
Filters, dashboards, or software boards are not included in the analysis of dependencies, therefore, none of these objects will be identified as using other objects.
Objects (for example a custom field) that are used used only by by filters, dashboards, or software boards will not be included in the report.