Link to Jira fails - due to missing values for some mandatory fields

For now, we have marked those fields as optional and going ahead.
FYI.. It creates an issue of type 'Task' and not 'Bug' just in case anyone is interested in knowing. Since we were trying to know which template needs to be fixed in order to proceed.

Hi Deepak,

You've found the way to go ahead, that's perfect. For information, which fields were mandatory on your side?

This first version of the JIRA plugin - which can create issues on a JIRA server, can and will be improved in the future to be more customizable so that it's easier to integrate it in customized workflows. For instance, we should make it possible to decide which kind of issue to create - as you said it is currently a 'Task'.

Thanks man.

Also wanted to add one more possible feature - Currently there is only a single "Link to Jira" button for a particular Issue. We also wanted to see a possibility of linking ALL or a specific set of violations reported by Sonar to a Jira Issue and track them in Jira. Currently its very cumbersome to go to each issue and click on the button to link it to Jira. If an option is available at a higher level either in the review page or violations page to link all the violations to Jira then it would be helpful.
Thanks.
Have also created an Improvement task for the above item : SONARPLUGINS-2423

Hi Guys, Is it possible to change the error message for not connecting to JIRA due to Mandatory fields. currently it is only show's impossible to connect to JIRA. If error message pops up saying its due to mandatory fields or some thing like this. It will be helpful to users.
Thanks
Amar

We are experiencing the same problem; the compulsory field in our Jira config is Component. Ideally, we'd like to be able to do two bits of tuning:

• specify issue type (although we can live with Task for the moment)
  * specify component within project (don't really see a nice way to work around this, I'd rather not make this optional for all non-Sonar users…)

In the interim, as amarkhot mentioned, it would be useful to reflect the soapenv:Fault faultstring back to the user, we found it "com.atlassian.jira.rpc.exception.RemoteValidationException:
{components=Component/s is required.} : []" by sniffing the TCP traffic in the end.

@Robin SONARPLUGINS-2549 Created to allow configuration of components.

Error message when there is a validation exception (for example when a mandatory field is not set) will now be displayed in Sonar UI, helping users to understand the cause of failure when creating a JIRA issue.

Concerning mandatory fields that are not populated by default by Sonar, we are suggesting that people create a new JIRA issue type and use it when creating issues from Sonar reviews (thanks to SONARPLUGINS-2548). For this new issue type simply make fields optional.

For reference, entry of the JIRA Plugin FAQ: http://docs.codehaus.org/display/SONAR/JIRA+Plugin#JIRAPlugin-FAQ