Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null
Skip to end of banner
Go to start of banner

Pattern match condition - Cloud

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Background

The regular expression based pattern-match condition is a powerful way to automate workflows. It gives workflow designers, great control over the actions performed on transition issues.

Pattern match condition

Pattern match condition is a highly flexible way that uses Substitution variables to match the issue information with a regular expression (regex). Although this method is a bit complex and less widely used for simple cases, it is a very powerful tool for covering many use cases. The simple cases can still be done with little knowledge of regular expressions. All the standard Substitution variables can be used.

Regex qualifiers

Qualifiers are used to make is easier to construct a regex pattern that matches the user scenario.

Exact

When looking for patterns, one can either find something that matches the pattern or you can do an exact match on the pattern. Doing find is usually easier and covers most use cases, but is not as precise as doing an exact match. The default is Find. Select the Exact checkbox if needed to be more precise. 

ValuePatternFindExact Match
abcabc(tick)(tick)
abcab(tick)(error)
abcac(error)(error)
abcb(tick)(error)
abc.*b.*(tick)(tick)

Literal

Regex has various characters that have special meaning. These characters need to be escaped (using \) if you want the character to not have special meaning. In some cases, you want to ignore all special character meaning and match on the literal string. Use the Literal checkbox to treat the pattern as a literal string.

ValuePatternNormalLiteral
abc.bc(tick)(error)
.bc.bc(tick)(tick)
abcabc*(tick)(error)
ababc*(tick)(error)
ababc+(error)(error)

Negative

Regex can be difficult when you want to condition on something not matching. The Negative checkbox makes it easy to reverse the condition so that the condition is true if the match is false and vice versa.

ValuePatternNormalReverse
abcabc(tick)(error)
xyzabc(error)(tick)

\S+(error)(tick)

Case sensitivity

Regex patterns, by default, are case sensitive. Use the embedded flag (?i) to get case insensitive matching.

ValuePatternNormal
ABCabc(error)
ABC(?i)abc(tick)

Or conditions

ValuePatternNormalNotes
aa|b(tick)
ba|b(tick)
abc(abc)|(xyx)(tick)Use ( ) or (?: ) for grouping



More information

Links to resources related to conditioning

More on regex pattern matching with examples

How to use regular expressions 

Tips

What if I don't need conditions?

Just leave blank (default).

Regex references

Concise summary of regex pattern syntax and special characters - Java pattern 

Reference - Regex expressions 

Watch out for regex reserved characters

Unless you use literal, you need to be sure any regex reserved characters you use are intentional. Otherwise, you must escape them with \

Examples: * + ( ) { } |

Test your regex interactively before you implement your workflow conditions using one of the regex testing websites like: RegexPlanet.

Conditions must both be met

If more than one condition is specified, both must be satisfied (the conditions are anded). Most OR conditions can be done through a single (more complex) regex pattern. See the tip below.

What if I have more than 2 conditions?

Regex patterns can be constructed to handle many situations that involve multiple comparisons.

Example

ValueRegex
Priority: %original_priority%, Status: %original_status%Priority: (Blocker|Critical|Major), Status: (Open|In Progress)

RegexPlanet results

Tutorials


Use this link to find all tutorials available in the Create on Transition for Jira documentation.

  • No labels