Versions Compared

Version Old Version 1 New Version Current
Changes made by

Jack Nolddor

Jack Nolddor

Saved on

Key

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

Description:

Excerpt

Searches issues that have been moved from one project to another. Additionally, you can further refine your query by specifying either or both the source and destination project.

Note:

You can use the asterisc symbol (*), in both source and destination project arguments as a keyword for refering to 'any project'.


Syntax

movedIssues()
movedIssues(sourceProject)
movedIssues(sourceProject, destinationProject)

Available sincev2.0.0-RELEASE
Supported fieldsIssue
Supported operatorsIN , NOT IN
Unsupported operators

= , != , ~ , !~ , > , >= , < , <=

IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Examples:

• Find issues that have ever been moved from one project to another:

Code Block
languagesql
themeConfluence
issue IN movedIssues()

• Find Stories that been moved from EMEA project:

Code Block
languagesql
themeConfluence
type = Story AND issue IN movedIssues("EMEA")

• Find Bug Bugs that been moved to LATAM project:

Code Block
languagesql
themeConfluence
type = StoryBug AND issue IN movedIssues("*", "LATAM")

• Find 'Open' issues that been moved from EMEA to LATAM project:

Code Block
languagesql
themeConfluence
status = Open AND issue IN movedIssues("EMEA", "LATAM")

Real World Use Cases:

· JRASERVER-41039 - Ability to search for issues that were moved (by Ismael Olusula Jimoh)
· How to find issues that were moved from one project to another (by srinivasp at ATLASSIAN Community)
· View issues that have been moved from one project to another (by Kristin Bestla at ATLASSIAN Community)

JQL Function Reference

Page Tree
rootJQL Function Reference
startDepth2