Introduction

With ScriptRunner Enhanced Search, users can utilize JQL functions and save them as filters for use in Atlassian's JQL search.
This means that you will be able to use it with TISSUE Cloud!

Background

To give a comprehensive background, users can refer to Atlassian’s example of how SQL joins works.

Image Removed

Example

Table 1

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

Image Added

Example

Primary Set of Issues

Key	Summary	Linked Issue
TASK-1	To perform UAT	Subtasks-1
TASK-2	To scan for bugs	Subtasks-2

Table 2Secondary 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

Head to ScriptRunner Enhanced Search
Enter your JQL
Check that the issues displayed are what you expect
Save JQL as a filter
Update the filter options as required
Use the new filter in TISSUE by modifying the JQL
Code Block
filter = <"YourCreatedFilterName">
You will be able to see the same results shown in Step 3 in your TISSUE Gadget