Frequently asked questions about configurations, capabilities and functionalities.
Post functions
I added a post function in the Create transition and it does not work.
| Possible cause | Solution |
|---|---|
| The issue has been added prior to the Creates issue originally default Jira post function. | Move the post function to a posterior position, always after the Creates issue originally post function. |
The post function Transition issue launches an error when it is executed.
| Possible cause | Solution |
|---|---|
| There is a condition or a validator in the transition that the post function executes. | Check the options Ignore conditions, Ignore validators and Ignore project in the section Additional options of the JWT post function Transition issue. |
I try to add new labels, but old labels are removed.
| Possible cause | Solution |
|---|---|
| The field Label is used for updating the labels instead of the New labels field. | Select the New labels field in the post function and use the same expression. |
When I send an email with the Send email post function, the key of the issue does not have an hyperlink and cannot redirect the user to the issue.
| Possible cause | Solution |
|---|---|
| The field code %{issue.key} will only return the key of the issue without hyperlink. | The solution is explained in the use case Add a hyperlink to an issue in an email. |
Automation rules
My automation rule is running the action on many issues but I only want to evaluate one.
| Possible cause | Solution |
|---|---|
| The JQL selector was added to the automation rule instead of the JQL condition. | Replace the JQL selector with a JQL condition. |
My automation rule only works when I remove the condition.
| Possible cause | Solution |
|---|---|
| The expression used for the condition is incorrect. | Test the expression in the Expression parser test page after selecting the corresponding issue and removing the trigger and selector contexts from the field codes of the expression. |
| The type of condition used is incorrect. | JQL conditions evaluate the issues based on a JQL query while Boolean conditions do it based on parser expressions. |
| The elements are not in the correct order. | Order the elements of the automation in a stairs-like position (from left to right) instead of a ladder-like position (from top to bottom). |
I can only add a few actions after a Scheduled trigger.
| Possible cause | Solution |
|---|---|
| At least one issue must be selected to perform most of the actions. The Scheduled trigger does not select a particular issue by default. | Use a JQL selector to select at least one issue. |
Expressions
I run an expression in the expression editor, but it returns almost the same text.
| Possible cause | Solution |
|---|---|
| The Basic text parsing mode was selected instead of another parsing mode. | Select the appropriate parsing mode. |
Everything works correctly when I test a calculation in the expression editor, but it fails when testing the whole implementation.
| Possible cause | Solution |
|---|---|
| One of the numeric field codes returns a null value, producing an error in the calculation. | Evaluate first if the values are null with a ternary operator and, depending on the outcome, perform different operations. |
I am doing a very simple calculation in Numeric mode, but I get a syntax error.
| Possible cause | Solution |
|---|---|
| The percentage sign of the numeric field codes has not being removed and the numbers are returned as texts instead of as numbers. | Remove the percentage sign of the numeric field codes. |
ScriptRunner field should be working in my calculation, but it does not.
| Possible cause | Solution |
|---|---|
ScriptRunner fields return a text instead of a number. | Convert the text to a number with the toNumber() parser function if possible. |
Other FAQs
Will my JWT license for Jira Server be functional after its expiration? Will I lose any functionality?
Even if the license for the app does not have active maintenance, the app can still be used without any functional restrictions.
However, without active maintenance, no updates/bugfixes/hotfixes and no support is available via our portal.
If you still have questions, feel free to refer to our support team.
