Copy Parsed Text to a Field post-function is a general purpose tool for setting almost any kind of field (text, select, radio button, multi-select, checkboxes, cascading select, multi-cascading select, user, multi-user, dates, date-time, number, etc). Although, in the case of field types Number, Date, Date-Time and Priority (when using associated numeric value) it’s usually preferable to use post-function Mathematical and date-time expression calculator, since you can enter complex math and time expressions.
Text to be parsed in the example is: "Current issue has key" + %{00015} + ", was created by " + %{00005} + " on " + %{00009} + ", and its Summary in uppercase is \"" + %{00000} + "\"."
Note that:
%{00015}
is field code of "Issue key"%{00005}
is field code of "Reporter's full name"%{00009}
is field code of "Date and time of creation"%{00000}
is field code of "Summary"Composing dynamic text by inserting field codes with format %{nnnnn} among text string literals. These field codes will be replaced at transition execution with the values of the corresponding fields. The resulting text will be copied into Target field.
Text to be parsed is: Current %{00014} issue was created on %{00009} by %{00005} in project %{00019} with summary %{00000}. It affects %{00077} versions, and is expected to be resolved on %{00012}.
Once configured, transition will look like this:
This is a very versatile feature that allows you to set the value of any custom field or issue feature in almost any way you may require.
Field type | Expected values and format when setting the field by a post-function | Examples |
---|---|---|
Checkboxes | Comma separated list of options to be selected. Admits + and - prefixes to add and remove single items. |
|
Radio Buttons | Name of the choice to be selected. | |
Select List (single choice) | Name of the choice to be selected. | |
Select List (multiple choices) | Comma separated list of options to be selected. Admits + and - prefixes to add and remove single items. |
|
Select List (multi-level cascading) | Multi-Level Cascading Select app supported: comma separated list of values for each level of the cascade. | America, USA, California, San Francisco |
Text Field (single line) | Text value (any other type will be cast to text) | |
Text Field (multi-line) | Text value (any other type will be cast to text) | |
Labels | space separated list of labels. Admits + and - prefixes to add and remove single items. |
|
Group Picker (single group) | Name of a group. | Administrators |
Group Picker (multiple groups) | Comma separated list of group names. Admits + and - prefixes to add and remove single items. |
|
User Picker (single user) | Name of a user name (not full name) or name of a project role. For project roles please make sure to set up a default user for a project role (Example 1) before. Supported apps: Issue Alternative Assignee | john |
User Picker (multiple users) | Comma separated list of user names (not full names), name of a group (every user in the group will be set), or name of a project role (every user in the project role will be set). Admits + and - prefixes to add and remove single items. |
|
Version Picker (single version) | Version name. | 1.0 |
Version Picker (multiple versions) | Comma separated list of version names. Admits + and - prefixes to add and remove single items. |
|
Project Picker (single project) | Project key or project name. |
|
Issue Picker | Issue Picker app supported: comma separated list of issue keys. Admits + and - prefixes to add and remove single items. |
|
Sprint | Jira Software's Sprint field can be set by writing on it the numerical ID of a Sprint. | Sprint's numeric ID can be obtained by moving the mouse pointer over some controls of JIRA UI as shown in this screenshot.
|
Customer Request Type | JSD's Customer Request Type field can be set by writing on it a Request Type's key. | Request type keys can be obtained by executing Copy a parsed text to a field post-function for writing the value of a field Customer Request Type with different values. A Request Type key begins by a project key followed by /. The default Request Type keys for a project with key ISD are:
Requires version 2.2.28 or higher. |
"Account" and "Team" TEMPO Timesheet's custom fields | Values used for setting these fields are internal numerical IDs. These IDs can be found out.
|
|
Note: All the examples above are shown in double quotes for readability, but if you are using basic parsing mode you should remove them.
This post-function provides 2 parsing modes:
+
or -
)Syntax specification:
Fields will be set with all valid options or items available for it that fulfills a certain regular expression (syntax: "/regexp/"), or not fulfilling it (syntax: "//regexp/"):
You will often use Copy Parsed Text to a Field in combination with other post-functions, like Write field on linked issues or sub-tasks, Update issue fields and Set a field as a function of other fields.
You should select an Ephemeral field in parameter Target field, in order to hold a temporary parsed text that will be used by the next post-function. In the case of post-functions Write field on linked issues or sub-tasks and Update issue fields the resulting parsed text stored in an ephemeral field will be written into a field in other issues (linked issues, transitively linked issues, sub-tasks, sibling sub-tasks, or any issue returned by a JQL query).