Skip to end of metadata
Go to start of metadata
On this page


Purpose

This post-function allow setting the value of a field in linked issues or sub-tasks using any of the following source values:

  • Field in current issue: the value a field in current issue.
  • Parsed text (basic mode): a text composition where value of fields in current issue can be inserted.
  • Parsed text (advanced mode): a string expression where we can use values of fields in current issue (syntax %{nnnnn}), and in linked issues and sub-tasks (syntax ^%{nnnnn}). Here we can use all the functions available in the Expression Parser.
  • Math or Date-Time expression: an expression returning a numeric value where we can use values of fields in current issue (syntax {nnnnn}), and in linked issues and sub-tasks (syntax ^{nnnnn}). Here we can use all the functions available in the Expression Parser.

Issues that can be written:

  • Linked Issues: issues linked to current issue
  • Sub-task: current issue's sub-tasks
  • Sibling Sub-tasks: when current issue is a sub-task, its parent's other sub-tasks


Example: Add attachments from current issue to cloning issues




Once configured, post-function looks like this:



Configuration Parameters

Filtering Conditions

Issues to be written can be filtered by:

  • Issue link type: only for linked issues.
  • Issue types: if no issue type is selected, then no filter by issue type is applied.
  • Statuses: if no status is selected, then no filter by status is applied.
  • Project: three possible options are available ("any project", "current project" and "any but current project").
  • Field values: when a boolean expression is entered, only those issues fulfilling the expression are selected. In this expression we use ^ prefix for field values in foreign issues (linked issues, sub-tasks and sibling sub-tasks): ^{nnnnn} and ^%{nnnnn}, while field codes without prefix correspond to current issue's field values.
    Example 1: boolean condition {00012} <= ^{00012} will require that issues have "Due Date" equal or later than current issue's "Due Date".
    Example 2: boolean condition %{00074} ~ ^%{00074} AND ^%{00017} in ["Blocker", "Critical"] will require that issues have "Fixed versions" contained in current issue's "Fixed versions" and that "Priority" has values "Blocker" or "Critical".

Additional Options

  • Don't overwrite target field if it's already set: when checked, this parameter will make the post-function do nothing in case target field is not empty in current issue.
  • Write linked issues and subtasks recursively: transitively linked issues and its subtasks are also selected provided they fulfill filtering conditions. This recursive operation is performed with no depth limit, but each selected issue is written only once.
  • Run as: Jira user post-function is going to be executed as. This parameter can be set to a fixed user (e.g. "john.nash"), or to a user field (e.g. "Reporter", "Assignee", etc). This parameter is important when we have permission or security restrictions that might prevent fields from being read or written.