We have an issue with validations on multilevel cascade select.
Issue #298
resolved
Hello Team,
We are using multilevel cascade plugin for jira. https://marketplace.atlassian.com/plugins/com.sourcesense.jira.plugin.cascadingselect/server/support
Validation on 3rd drop-down are not supported with workflow tool box. Could you please verify and let us know it there any way to implement it?
Comments (32)
-
repo owner
-
reporter
Hello Fidel,
Thanks for the update, I have upgraded the plugin to the newer version now I'm facing issue with null comparative on multi select field. Please find the below syntax.
(%{14400.2}=null)
We have field with above ID and above condition is always returning true kindly verify and provide an update on this.
Thanks, Srini.
-
repo owner
Hi Pudi,
Which version of the plugin have you installed?
Can you please attach a screenshot of feature of the plugin where you are using the comparative? I would like to see the whole configuration of the feature.
-
reporter
Hello Fidel,
I'm using Version:2.2.9, and please find the screen shot of configuration I made. [image: Inline image 1]
Thanks, Srini.
-
repo owner
Pudi, there isn't any image attached to the issue.
-
reporter
[image: Inline image 1]
-
reporter
Please find the above screen shot,
Thanks, Srini
-
repo owner
Sorry Pudi, no screen attached to the issue. You have an option to attach files to the issue at "More" dropdown list, at the top-right of the screen.
You can also send me the file to support@workflowarts.com.
-
reporter
- attached Untitled.png
-
repo owner
Pudi,
I would like to find out the actual value that %{14400.2} is returning. Please, follow these instructions:
1) Disable the validation writing true OR %{14400.2} = null
2) Add "Copy a parsed text to a field" post-function with the following configuration:
- Target field: New comment
- Parsing mode: basic
- Text to be parsed: Returned value is: %{14400.2}
3) Now execute the transition. The validation will not fail because of the true term in the validation, and a comment will automatically be created with the returned value. Please, let me know the value you have obtained.
-
reporter
Hi Fidel,
No comment is added , Even if the 3rd value is present,
Kindly verify this from your also.
Thanks, Srini.
-
repo owner
Hi Pudi,
At least you should be getting a comment like:
Returned value is:I think that you are doing something wrong and you are not actually executing the modified workflow. Maybe you are forgetting to publish the draft, or you are using a different workflow scheme, or something like that.
Please, double check your configuration.
Anyway, can you please export your workflow as an XML file, and attach it to the issue?
-
reporter
- attached Error.png
Hello Fidel,
If I add a post function as you requested, It is blocking me to create issue.
Kindly check attached screen shot.
-
repo owner
Can you please attach the whole post-function's tab of your "Create Issue" transition? I would like to see all the post-functions your executing and the execution order.
-
reporter
- attached Capture.PNG
-
repo owner
You should move "Creates the issue originally" post-function to first position in execution order, otherwise you are trying to create a comment on an issue that doesn't exist.
Please, also edit parameter "Text to be parsed" with the following value:
Returned value is: "%{14400.2}"I have added double quotes in order to make visible any possible blank space.
-
reporter
Hello Fidel,
Returned value is: "" is the comment added for the ticket which does not have 3rd vlaue
Returned value is: "QA Processing Question" is the comment added for the ticket which has 3rd value
-
repo owner
Please try the following boolean expression in your validator:
%{14400.2} = "" -
reporter
It is not working :(
-
repo owner
Pudi, there is a bug in the plugin linked to Multi-Level Cascading fields when edited in transition screens. I have fixed the problem in version 2.2.10_beta_4.
Please, let me know if this new version fixes your problem.
-
reporter
It Is not working with the condition
"%{14400.2}!=null"
-
reporter
I need a validation to make 3rd level should be mandatory, and please add "vikas.basra@dealertrack.com" as watcher for this
-
repo owner
Pudi, could you please double check that you have correctly installed version 2.2.10_beta_4? There was actually a bug that was causing the problem, but now it's fixed. You should previously uninstall your current version of the plugin before uploading a new version as a .jar file.
If you keep having problems I would like to have a screen-share by Skype in order to see the problem in direct.
I can't add an email as watcher. Please, ask your college register at Bitbucket and add himself as watcher.
-
reporter
Yea I have verified still the issue is persisting
-
reporter
At what time we can have call and screen sharing
Im sitting in India (IST time zone). we can plan it tomorrow
-
reporter
- we can have it now please find the below meeting details?
-
https://www1.gotomeeting.com/join/940948208 Toll-free dial-in number (U.S. and Canada): (866) 279-3652 Toll-free dial-in number (India-Mumbai): 180030709800 Conference code: 5167343826
-
repo owner
Hi Vikas,
I have found that there is another problem when doing comparisons of type != null. I have fixed it in version 2.2.10_beta_5.
Please, try it and let me know whether it solves the problem.
-
repo owner
Hi Vikas, I have edited my previous post and fixed the link to the version.
-
repo owner
Use this link: 2.2.10_beta_5. It's the same as the one in my former post.
-
repo owner
Vikas, I can be available at 17:00 UT, i.e., in 35 minutes approximately. Is that time ok for you?
-
repo owner
Hi Vikas,
Version 2.2.10_beta_6 fixes the problem. This version has passed all the regression tests, so you can use it in production environment safely.
You can use the following boolean expression:
%{14400.2} != null -
repo owner
- changed status to resolved
Fixed in just released version 2.2.10.
- Log in to comment
Hi Pudi,
Multi-Level Cascading custom fields are already supported by JIRA Workflow Toolbox, but you should install version 2.1.25 or higher.
In order to reference 3 level in a Multi-Level Cascading field should use the following syntax %{nnnnn.2], where nnnnn is the field code of the field.