Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
Table of Contents

JQL Functions

STAGIL Assets introduces new JQL functions that can be used in the advanced issue search and STAGIL custom fields.

issue in relation("","",...,"")

The add-on provides a new JQL function to find all your issues within certain relations. It gives you a list of all related issues, searching from a start node over the given relations. You can also use the parameter “all” in order to search through the entire link network (It may impact your search performance).

...

Level - Provide the depth of your relation as "level1", "level2", "level3" or "level4". Maximal depth is 4.

issue not in relation("","",...,"")

This JQL function works exactly as “issue in relation” but will give you the negation of it: all issues that are NOT in relation that you have defined.

JQL Examples

Panel
titleFind Organization of a Contact CRM-18
Code Block
issue in relation("key = CRM-18", "Organization-Contact", "level1")
Panel
titleFind other Contacts in the same Organization like CRM-18.
Code Block
issue in relation("key = CRM-18", "Organization-Contact", "level2")

You only use the relation "Organization-Contact", but go two levels. First from Contact (CRM-18) to Organization (find CRM-10) and then to other Contacts connected (find CRM-19).

Panel
titleLimit the scope of results

Code Block
type = Contact AND issue in relation("key = CRM-18", "Organization-Contact", "level2")

Panel
titleFind Task and Subtasks of an given EPIC

You can also use the standard link type of JIRA.

Code Block
issue in relation("key = EPIC-1","Epic-Story Link","jira_subtask_link" ,"level2")

This search shows where EPIC-1 is a key of some Epic.

JQL Variables

Usage only in STAGIL Assets Dynamic Dependend and  STAGIL Assets Lookup fields. 

...

Note

Use apostrophes in case the data to pull contain spaces in between. Example: '{source.customfield_id}'

{sourcekey}

Provides the key of the issue, where the assets field is located in.

{projectkey}

Provides the key of the project of the issue, where the asset field is located in.

{reporter}

Provides the reporter (as user) of the issue, where the assets field is located in.

{currentusermail}

Provides the mail address of the current User who is logged in.

{mail.reporter}

Provides the mail address of the reporter.

{mail.assignee}

Provides the mail address of the assignee.

{mail.customfield_12345}

Provides the mail address of a single user picker custom field.

{source.customfield_id}

Provides data pulled from a selected customfield, based on the current source issue. 

{source.summary}

Provides the summary of the current issue.

currentUser()

Provides the name of the user who is currently logged in. 

searchingUser()

Provides the name of the user who is running the search (can be defined in the configuration menu of asset customfield).

JQL Variable examples

Panel
titleShow all issues, where fixVersion is the same as in current source-issue

This JQL in a Lookup field in an assets issue finds all issues, where fixVersion is the same as in {source.customfield_16404}

Code Block
fixVersions in ({source.customfield_16404}) 

...