ūüöĬ†JWT 3.0 is out¬†ūüöĬ†

The app was completely overhauled, and so was the documentation: Jira Workflow Toolbox (Server/Data Center) Home

The page you are viewing is still valid for all app versions prior to 3.0.

On this page


Features used to implement the example



Example: Restrict sub-task type creation depending on parent issue type

I suppose that you have one issue task called "Sub-task" and you want to restrict its creation only to "Task" parent issue types. In that case you have to add validator to transition "Create Issue" of the workflow used by "Sub-task", with the following configuration:

 


Text to be parsed is: %{00014} = "Sub-task" IMPLIES %{00040} = "Task"


Note that:

  • %{00014}¬†is field code for¬†"Issue type"
  • %{00040}¬†is field code for "Parent's issue type"
  • Logical connective¬†IMPLIES¬†is available since version 2.1.22. If you have installed a previous version, you can use the following equivalent expression:¬†%{00014} != "Sub-task" OR %{00040} = "Task"


Once configured, the transition Create Issue will look like this:


Other variation of the usage example

Avoid any type of sub-task creation only to parent issue types "Bug" and "Enhancement"

%{00041} = null IMPLIES %{00040} not in ["Bug", "Enhancement"]

being %{00041} field code for field "Parent's issue key"

an equivalent expression without using connective IMPLIES and operator NOT IN:

%{00041} != null OR %{00040} != "Bug" AND %{00040} != "Enhancement"


Avoid "Sub-task" type creation only to parent issue types "Bug" and "Enhancement"

%{00014} = "Sub-task" IMPLIES %{00040} not in ["Bug", "Enhancement"]

or an equivalent expression without using connective IMPLIES and operator NOT IN:

%{00041} != "Sub-task" OR %{00040} != "Bug" AND %{00040} != "Enhancement"


Limit "Sub-task" type creation only to parent issue type "Task", and "Agile Sub-task" type creation only to parent issue types "Story" and "Epic"

(%{00014} = "Sub-task" IMPLIES %{00040} in ["Task"]) AND (%{00014} = "Agile Sub-task" IMPLIES %{00040} in ["Story", "Epic"])

or an equivalent expression without using connective IMPLIES and operator IN:

(%{00014} != "Sub-task" OR %{00040} = "Task") AND (%{00014} != "Agile Sub-task" OR %{00040} = "Epic" OR %{00040} = "Story")




Other examples of that function

Related Usage Examples