I have 2 fields named X AND Y.
X is a test filed
Y is a drop down field having values like India, Srilanka etc.
Requirement -
Customer will give some value in X field, system will check whether that field is present in Y or not, if not need to add that value in Y field.
Is it feasible we are using JIRA server version.
It sounds like you want to use something like the cascading select field. This field type gives you two dropdown menus - whichever value you choose in the first dropdown determines which values you should select in the second dropdown. However, this does not achieve the validation you're looking for (i.e. make field Y required if some value is chosen in field X).
For that kind of validation, I would check out the Behaviours module of the ScriptRunner add-on. With this module, you can add a behavior that can make certain fields visible/hidden or required/optional based on field selections, which should cover the requirement you've outlined.
i am sorry this is not my ask?
I have two different fields X (text field)and Y(Drop down), at the time of creation of the issue what i want is when we enter some value in X field it should check the values of the Y field and if the value is new it should be added to Y field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You'll need to write some code to do that. A post function could catch the update and check values.
However, an more simple solution would be to just use a labels field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How the label field will be of help here ? can you please explain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How the label field will be of help here ? can you please explain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The label field proposes existing labels when a user starts typing, and if they don't like any of the existing ones, lets them add a new label.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But that would be for one single field.
I have two fields X and Y, X is test and Y is drop down.
While creating the issue i will enter a value in X , then the system should check whether that value is present in Y or not, if not it should add that value in Y.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But that would be for one single field.
I have two fields X and Y, X is test and Y is drop down.
While creating the issue i will enter a value in X , then the system should check whether that value is present in Y or not, if not it should add that value in Y.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, using a label field would mean you can discard a redundant field (Y is your real data, X is useless after a new option has been added to Y). A single label field fulfils your need without a redundant field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.