DC Use Cases





SHOW YOUR SUBTASK VALUES ON PARENT & SHOW ANY ISSUE’S ANY FIELD
HERE YOU CAN SEE A CONFIGURATION EXAMPLE WITH BOTH SUBTASK AND CUSTOM FIELD SOURCES

 

 

 

The configuration name is a required field and you will be using it to define field relations.

 

Here you should select a project to display fields and you can restrict the Related Issue Fields panel to a project role or a group. 

You can leave Permission Configuration blank if there is no need for view restriction. 

 

 

 

 

 

In Field Source Configuration, you can have more than one source configuration. Here we have two of them. 

 

 

In CF named configuration, Custom Field is selected as a Field Source and in the Custom Field section you need to pick a text field issue. 

In this example, the "Issues" field is a text field. 

You should write the issue keys in the Text Field so that the specific issues' information will be displayed in the Related Issue Fields panel. Also, you can use the Additional JQL Filter area to narrow down the issues. For example, you may want to display only In Progress issues' information in the panel.

 

 

 

 

 

 

In subtask named configuration, SubTask Issue is selected as a Field Source. If you need to see a specific subtask type, you can specify it by typing JQL.

 

 

Here, select the fields you want to display. According to the configuration, we will see the Key, Summary, Due date, Start date and Priority fields of subtask and issues that are written in the Issues field in the display issue. 

 

 

 

 

 

 

 

In-display issue, values pops up when you hover the mouse over "Multiple Values"

 

 

 

SHOW SLA FIELDS ON SOFTWARE ISSUES
HERE YOU CAN SEE A CONFIGURATION EXAMPLE WITH THE LINKED ISSUE SOURCE

 

 

The configuration name is a required field and you will be using it to define field relations.

 

 

 

Here you should select a project to display fields and you can restrict the Related Issue Fields panel to a project role or a group. 

You can leave Permission Configuration blank if there is no need for view restriction. 

 In Field Source Configuration, you can have more than one source configuration. Here we have just one of them.

 

 

 

In Linked Issue configuration, Linked Issue is selected as a Field Source. JQL option can be left empty, if so, it means you will see any linked issue’s fields.

 

Here, we specified Bug/Request Service Management project so we want to see service management issues’ SLA fields on our specific software project.

 

 

 

 

 

Here, select the fields you want to display. According to the configuration, we will see the Key, Summary, Status, Impact, Urgency and SLA fields of the linked issue in the display issue. 

 

 

 

In-display issue:

 

Â