Hello,
Unfortunately JIRA doesn't remove 'None' from a Cascading Select Custom Field when they are two values present. I came across have an improvement request to better handle this as tracked under JRA-32463. I would suggest that you do the following on the ticket:
* Vote, so that it will receive more attention
* Watch it, so that you will receive any and all updates
* Comment, and give your opinion on the matter
You could look at customising JIRA to prevent this kind of behaviour,
Hope it helps.
Regards,
Monique
I added the below JavaScript to the description of the cascading field in the field configurations. Worked for me.
#customfield_33382 = "id of the parent select list"
customfield_33382:1 = name of the child select list"
<script> |
AJS.$('#customfield_33382').children(':first').hide(); |
AJS.$('#customfield_33382').change( function (e){ |
setTimeout(function () { |
AJS.$('[name="customfield_33382:1"] option:first').remove(); |
}, 100); |
}); |
</script> |
Thanks
Andrian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a great workaround! Thanks so much.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andrian F This works good :) But after I add this to script, I get a NONE in the first drop down , even though I have a default value set for the field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I implemented this - so far so good. The problem is that as soon as I do a few manipulation on existing tickets (commenting, moving, etc.) and then create a new ticket, the "none" is back.
Checked with Firefox and Chrome, JIRA 6.3
Any idea, why?
Thanks and best,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you check if the JS is getting executed . Try to add some console.log("") messages and verify that.
Recently i came to know that, JS to be executed the user needs to have edit permissions on the ticket.
That could be one reason too
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.