3 Custom Field values depended on each other

[Rjve Nautiyal]

Hi,

I have currently 3 custom fields in JIRA with the field type as - single list of values in JIRA.

3 custom field name and drop down values- Portfolio- A,B,C Dev- Client1, Client2,Client,3,Client4, Client5, client6 QA- QA1,QA2,QA3,QA4

so what I am looking is whenever Portoflio-A is selected under dev fields- I should see only Client1 and Client2. And when I select client1 I should be able to select QA1 and QA2.

Is this can be done with the help of jira workflow toolbox please help.

Thanks & Regards, Rajeev Nautiyal

[Fidel Castro Armario]

Hi Rjve,

Sorry, it can't be done. What you can do with JIRA Workflow Toolbox is implementing a validation that checks whether the values selected at Dev and QA are compatible with the value selected at Portfolio. To do it you can use the following boolean expression:

(%{aaaaa} = "A" IMPLIES (%{bbbbb} in ["Client 1", "Client 2"] AND %{ccccc} in ["QA 1", "QA 2"])) AND
(%{aaaaa} = "B" IMPLIES (%{bbbbb} in ["Client 3"] AND %{ccccc} in ["QA 3"])) AND
(%{aaaaa} = "C" IMPLIES (%{bbbbb} in ["Client 4", "Client 5", "Client 6"] AND %{ccccc} in ["Qa 4", "QA 5", "QA 6"]))

replacing

• aaaaa with field code for Portfolio.
• bbbbb with field code for Dev.
• ccccc with field code for QA.

Like shown in the screenshot:

[Rjve Nautiyal]

Many thanks Fidel.

But here what is happening is my custom fields of Dev and QA will have nearly 15 drop down values, so when the users are creating the new issues for them it will be difficult to go with the nearly all 15 drop down values and then select the appropriate value.

Do we have any option wherein if I select Portfolio "A", In Dev I should see only Client1 and Client2 and when I select Client1 under QA- I should be able to see QA1 and QA2 only.

Is this possible.

Thanks & Regards, Rajeev Nautiyal

[Rjve Nautiyal]

Basically I am looking to hide the drop down values and it should get enabled as soon as I select the one of the drop down values

[Fidel Castro Armario]

Sorry Rjve, but it's not possible to do it using JIRA Workflow Toolbox.

[Rjve Nautiyal]

Hi Fidel,

As an alternate option I have installed "Multi-Level Cascading Plugin" and "JIRA workflow toolbox" Plugin is helping me up to some extend.

Here is what I did- whenever a users are selecting first level of values I am getting that value populated in other field (Text Field type with read-only) with the help of post function - Copy cascading select field. whenever a users are selecting second level of values I am getting those value populated in other field (Text Field type with read-only) with the help of post function - Copy cascading select field.

So, copy cascading select field in jira workflow toolbox is currently supporting only first level and second level.

Can jira workfow toolbox can support third level of values also so that I can use one more custom field (Text field type with read-only)

Could you please let me know if this possible?

Thanks & Regards, Rajeev Nautiyal

[Fidel Castro Armario]

Hi @rjvenautiyal,

Yes, you can copy any level of Multi-Level Cascading fields. To do it you should use "Copy a parsed text to a field" post-function with the following syntax:

• %{nnnnn.0}: 1st level
• %{nnnnn.1}: 2nd level
• %{nnnnn.2}: 3th level

and so on, replacing nnnnn with field code for the Multi-Level Cascading custom field.

[Rjve Nautiyal]

Hi Fidel,

Many thanks for quick reply.

One last thing I wanted to check- While creating the issues I am able to populate the values in the custom field for the multi-level cascading but when I edit the issues do we have any option in jira workflow toolbox which will help me to update the values in the custom field based on the multi level cascading because the post-function workflow triggers while creating the issue.

For eg- I created an issue with the Portfolio- A but later on I understand I have selected incorrect portfolio. So, when I change the portfolio to B. It should reflect in custom field as "B" currently which is not happening while editing the issues because the post function is trigger only for creation of issues,

Thanks & Regards, Rajeev Nautiyal

[Fidel Castro Armario]

There is a possible solution based on linking edition of Multi-Level Cascading field to a global-reflexive transition, i.e., a transition available to all the statuses of the workflow, and which doesn't change status, since it's only used to show the screen to the user in order to allow editing the Multi-Level Cascading custom field.

In issue Issue #575 there is a detailed explanation of how to do it. The field to be edited in that example is called Review Required.

Don't forget to add "Copy a parsed text to a field" post-function to the transition for editing the field.

Please, let me know if you have any doubt.

[Rjve Nautiyal]

Hi Fidel, Many thanks for your quick reply. And will update my comments for any doubt.

Thanks & Regards, Rajeev Nautiyal

[Rjve Nautiyal]

Hi Fidel,

Many thanks for quick help and support on this. Very much appreciated. The fields are getting populated based on the multi-level cascading -excellent plugin

Thanks & Regards, Rajeev Nautiyal

[Fidel Castro Armario]

Excellent!