Post-function "Parse field for extracting data" is aimed to make it possible for a workflow transition to extract specific pieces of information from a field by means of parsing the field's value.
It uses delimiters or/and format specifications of the value to be extracted for selecting the data fragments that will be extracted from the field's value.
This is an example of the post-function's configuration for extracting an email address from the last comment of an issue and writing it into a custom field called Email. The email is expected to be preceded by string "SENDER = ", with an uncertain number of spaces and ignoring the case. This is the configuration to do it:
Once configured, post-function's configuration look like this:
An example of the result of the execution of this post-function:
Proposed Usage Examples
- Parse Summary for setting issue Priority: setting Priority of an issue when we write the priority name between brackets in the issue Summary. This can be particularly useful for issues created by email.
- Parse Summary for setting Due Date: setting Due Date of an issue when we write "due on" followed by a date in the Summary of the issue. This can be particularly useful for issues created by email.
- Parse Description for creating Issue Links: creating issue links when writing sentences containing issue keys in issue Description.
Real Use Cases
- Copy a parsed text to a field: using advanced parsing mode you have a comprehensive set of formating functions at your disposal.