Conditional Rule validity is based on the following variables:
This page illustrates changes having impact on Conditional Rule validity and the way to restore it.
Notice that when a conditional rule is retrieved invalid the condition is assumed as not set and the user is alerted as showed on the following screenshoot:
In order to properly evaluate a Conditional Rule expression the user set on the Conditional Rule Settings needs Browsing permission on the Project on whom the Conditional Rule is going to be evaluated.
On setting or updating the user set, the add-on automaticaly grants the user of the Browsing permission on all Projects.
Changes having impact on user validity and the way to manage them is expleined bellow:
The Conditional rule expression expects a query using the JIRA Query Language (JQL) sintax.
The complete documentation of the JQL sintax is detailed on https://confluence.atlassian.com/display/JIRA/Advanced+Searching.
When creating or updating a Conditional rule expression the JQL check button returns confirm of expression validity:
A Conditional rule can be saved only if Conditional rule expression is valid and Rule Name isn't used already.
A valid Conditional rule can be invalidated later due to Conditional rule expression invalidation depending by different kind of causes (e.g. fields renaming, fields deletion, options renaming or deletion, etc).
Solution: In order to investigate why a Conditional rule expression isn't valid, apply the expression on the JIRA search navigator as showed bellow:
