Hi Lavanya,
I see the error you are getting here. That error is rather generic. It could be caused by the field configuration schemes in Jira not having that field appear on the create screen. However more often I find that this error happens because the user has not properly authenticated.
I'd be interested to learn more about how this integration is setup. Are you supplying an email / password for Jira Cloud in this Flow tool? If so then it might explain this as an authorization failure. First thing to check is the user account has the rights to create an issue in the project in question. If it can, then that tends to be a good indication that the account is ok here. If it cannot, then that's the first problem to overcome.
Since Jira Cloud and the Jira Cloud REST API to allow for unauthenticated requests, Jira doesn't always handle user authentication the way that some applications expect. Is the Microsoft Flow trying to use Jira's REST API to make this call? If so, then I'd be interested to understand how it's trying to authenticate here.
The most common method I would suspect would be the Basic Auth for REST APIs. If that's true, then you should be aware that we deprecated Basic authentication with passwords and cookie-based authentication back last year. You can still use basic auth, but you need to generate an API Token. Please note that if you do this, you can't just supply the token where a password was once accepted. Instead you need to first build a string of emailaddress:API_Token, then base64 encode that string, an then pass that encoded string in an authorization header that you pass when making the REST API call. These steps are documented in Basic auth for REST APIs as well.
I don't know if this Microsoft Flow integration can do that or not, but I have seen other integration tools get tripped up by this recently.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.