Skip to main content

transitionedBy

Overview

The transitionedBy function allows you to search for issues that have been transitioned to a specific status within a given time period, optionally filtered by the user who made the transition.

Syntax

issue in transitionedBy("subquery", "status", "start_date", "end_date", "user")

Parameters

  • subquery (required): A valid JQL query that defines the set of issues to evaluate
  • status (required): The name of the status to which issues were transitioned
  • start_date (required): The start date in format "yyyy/MM/dd HH:mm" or "yyyy/MM/dd"
  • end_date (optional): The end date in the same format as start_date
  • user (optional): The username or display name of the person who made the transition

Supported Operators

  • in - issues matching the criteria
  • not in - issues not matching the criteria

Examples

Finding issues transitioned to "In Review" within a date range

issue in transitionedBy("project = SER", "In Review", "2023/01/01", "2023/05/01")

Finding issues transitioned to "Done" by a specific user

issue in transitionedBy("project = SER", "Done", "2023/01/01", "2023/12/31", "jsmith")

Finding issues transitioned to "In Progress" since a specific date

issue in transitionedBy("project = SER", "In Progress", "2023/06/01 10:00")

Finding issues not transitioned to "Done" by a specific user

issue not in transitionedBy("project = SER", "Done", "2023/01/01", "2023/12/31", "jsmith")

Performance Considerations

  • The function analyzes all changelogs from issues matching the JQL subquery, which may take significant time to complete
  • Using specific date ranges and user filters can improve performance

Error Handling

The function will return an error if:

  • Invalid status names are specified
  • Invalid date formats (must be "yyyy/MM/dd HH:mm" or "yyyy/MM/dd")
  • Non-existent users are specified
  • Invalid JQL queries
  • changedBy - Search for issues where fields were updated
  • commented - Search for issues with specific comment criteria