Project Configurator for Jira

All Adaptavist Apps

Page tree

This documentation has moved. For the most recent documentation, check out https://docs.adaptavist.com. Please update your bookmarks and links.

Skip to end of metadata
Go to start of metadata

Note

From version 3.0.8 of Project Configurator, the Used By Report has been renamed the Object Dependencies Report. The report's purpose and output remain unchanged. 

This report is a new feature available in Project Configurator v2.2.0 or newer.

This report shows you, for all objects that are directly or indirectly part of the configuration of any project in your instance, where they are being used or referenced by other configuration objects. For example, you may need to know:

  • If custom field "Technology" is used in any workflow?
  • What is the relation between a custom field and a project?
  • Where a group is referenced, including role members, permissions, issue security schemes, workflows, etc?

The Used By report provides a quick answer to questions like these.


How to Use It

The Used By report can be launched from the same menu where you can export and import projects. The analysed objects are grouped into tabs according to their type, for easier navigation.


When an object appears as a link, clicking it changes the current tab to the tab for the clicked object and the page scrolls to the object's position, if necessary. Clicking in these report links allow you to easily navigate and track long chains of object dependencies. For example, clicking on any of the links above for workflow objects take us to the "Workflow" tab, as seen below:

When a referencing object appears more than once, this means that the referencing object contains more than one reference to the used object. 

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 will never be 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 the configuration, i.e. the objects where one can start looking for the rest of configuration objects that are being used. 
  • Currently filters, dashboards or Agile boards (either Scrum or Kanban) are not included in the analysis of dependencies. This means that:
    • none of these objects (filters, dashboards, boards) will be shown as using other object
    • objects (for example a custom field) that are used only by filters, dashboards or Agile boards will not be included in the report