I'm sorry, but "not an option" is not an option you have the luxury of here.
If you're going to rule out understanding the code and recompiling it properly, then your only other valid option is to remove the plugin. It's not working, it's not going to work, so you can't use it.
Passing in <null> instead of what is expected really isn't going to help you in the slightest - the best result you get from any real language is going to be "I expected you to pass me a valid object of type <what you already had from the api>". Oh, and coding to accept null gracefully is generally a bad idea too - it tells us you haven't thought through problem very well (just because a lot of people do it, doesn't mean it's clever - think about drinking, homeopathy or overeating...)
Which means you need to write the code to get the right object. It's not a case of trying to pull in other references or pointers, it's a case of changing the code to work out and pass in the right thing. Sticking random nulls in really is not an option either - the parameters are there for a reason.
Bother, I've just realised, I kept saying "you" there. You can, of course, find someone who knows java. Or better, someone who knows Jira's API well enough.
Posting the function call you're making here might prompt someone to point you in the right direction,
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot