Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

The Tissue Gadget use the issues from the primary set of issues to join up with linked issues from the secondary set of issues.
It will display blank values when there is no linked issues. This is similar to a Left Join in database terminology.

In some cases, the users may only want to display rows which have matching linked issues.
The Inner Join will skip those issues in the primary set of issues which does not have linked issues

SQL Join.png

Example

Primary Set of Issues

Key

Summary

Linked Issue

TASK-1

To perform UAT

Subtasks-1

TASK-2

To scan for bugs

Subtasks-2

Secondary Set of Issues (to be linked)

Key

Summary

Linked Issue

TASK-2

To scan for bugs

Subtasks-2

TASK-3

To deploy to production

TASK-4

To standby for issues

Subtasks-2

How the tables will look in TISSUE gadget and ScriptRunner’s Enhanced Search

TISSUE Gadget is configured to work like a 'Left Join,' which means that all rows from Table 1 will be displayed, even if there is no matching value in Table 2.
Any missing data from the right table will show as empty values.


Left Join (Used by TISSUE gadget)

Key

Summary

Linked Issue

TASK-1

To perform UAT

Subtasks-1

TASK-2

To scan for bugs

Subtasks-2

TASK-4

To standby for issues

Subtasks-2

TASK-3

To deploy to production

ScriptRunner’s Enhanced Search, using an 'Inner Join,' will only display rows where there is a match between the two tables. If there are no matching records, those rows will be excluded from the result, meaning rows with empty values won't be shown


Inner Join (Possible through the use of ScriptRunner’s Enhanced Search)

Key

Summary

Linked Issue

TASK-1

To perform UAT

Subtasks-1

TASK-2

To scan for bugs

Subtasks-2

TASK-4

To standby for issues

Subtasks-2

Steps to achieve Inner Join

It is possible to use ScriptRunner Enhanced Search to filter the primary set of

  1. Head to ScriptRunner Enhanced Search

    ScriptRunner Enhanced Search.png


  2. Enter your JQL

    JQL Search.png

  3. Check that the issues displayed are what you expect

    JQL Search Results.png

  4. Save JQL as a filter

    Save JQL Search as Filter.png

  5. Update the filter options as required

    Save Filter Options.png

  6. Use the new filter in TISSUE by modifying the JQL

    filter = <"YourCreatedFilterName">

    Adding JQL to TISSUE.png

  7. You will be able to see the same results shown in Step 3 in your TISSUE Gadget

Before using Enhanced Search

After using Enhanced Search

Not using Enhanced Search.png

Using Enhanced Search.png

Reference

  • No labels