manuelbcd

me too, it would be nice to arrange something like a call together so that we could align

Hello @sonalp123 I think we know what is happening. The issue.Fields array is not present in creation response by default so you are trying to read a non populated field....

Hi @sonalp123 would you be so kind to confirm that your issue is resolved so that we can close it? Thank you

@sonalp123 would you be so kind to share with us what did the trick to resolve it?

@vbisbest @tuckyapps would you be so kind to specify jira version and type? Maybe I can bear a hand here Best.

Let me shed some light on this (if I understood the problem properly). @tuckyapps, @vbisbest you said you are unable to create issues when specifying reporter, using any username but...

Hey @tuckyapps. Sorry, maybe I did not express myself properly. username field is not deprecated, it is a valid field within user structures in both Jira server and Jira cloud....

It will work with Jira Server API but not with Jira Cloud API. If you are communicating with Jira Server API, you will be able to refer to users using...

If Jira Cloud is allowing you to create issues by specifying username without accountID it is probably because your project has a default assignee and reporter :) Please perform the...

Yes @kusuriya, i do agree. Im worried because im not sure if is worth adding this feature while breaking code compatibility. Actually I was asking about that in #368 If...