Off-the-shelf, no. Schemes are all hung off the project and issue type, so you can't have different field configurations by component. It would be messy if you could too - the code would have to dynamically change field settings on-screen part way through a create or edit screen, and you immediately run into a massive problem in that you don't know which scheme to use when the user selects more than one component.
There are two more obvious options here - bodge something in specifically for your needs with javascript, or write a validator that would kick in on issue transtions and check the data entered is valid.
I always prefer the second one myself (javascript fixes tend to break on any change or upgrade and can interfere with each other, whereas I've got validators written for Jira 3 which work in Jira 6 with little ore than "recompile for new version"). For both solutions though, I'd look to Jamie Echlin's work - for the front-end changes, you can probably avoid your own javascript and use the behaviours plugin. For the validator, his script runner plugin can save you a lot of time and coding.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.