web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate - Using Connectors / Problems using Jira V3
Power Automate - Using Connectors
Unanswered

Problems using Jira V3

(2) ShareShare
ReportReport
Posted on by vs07 4

I have created a flow that connects an MS Form submission to creating a Jira ticket. I am using V3 of the Jira connector. On some Jira boards this flow works ok, on others, it comes up with this error

 

The dynamic operation request to API 'jira' operation 'ListIssueTypesFields_V2' failed with status code 'BadGateway'. Error response: { "error": { "code": 502, "message": "Field 'reporter' of type 'user' is not supported. Please see connector documentation for more info.", "source": "europe-001.azure-apim.net", "path": "choose\\when[1]\\choose[1]\\when[4]", "policyId": "", "clientRequestId": "5a8beb97-d7c5-43ad-a2e2-ea8e6f29b905" } }

 

I get as far as selecting the Issue Type and it gives me this error. If I select another board, it works ok and I can make changes to the various fields. Can anyone tell me what could be the problem or how to fix this?

I have the same question (1)
  • jcaban Profile Picture
    jcaban 2 on at
    Re: Problems using Jira V3

    I recently started having this same issue with a flow that was previously working.

  • Mtc22 Profile Picture
    Mtc22 16 on at
    Re: Problems using Jira V3

    Hello

     

    This is a known limitation of this Action as per the official MS Documentation:

     

    The Create a new issue (V2) action supports only simple field types such as 'string', 'number', 'date', and 'datetime' in the dynamic schema. If project configuration has a required fields of complex data types, the operation will fail with the error: "Field '{key}' of type '{type}' is not supported". To workaround this, please change project fields configuration and make these fields not required.

     

    It says this about the V2 but I know the problem persist with the V3, I was never able to create a ticket using this Action because not every field is a string, some are multiple options, or a checkbox, etc.

     

    Most likely the field "user" is not a string but a list of options, which means is not supported by this Action. You either change that field to a string type, or my workaround was using HTTP POST Request and create a ticket using that an passing a JSON with all the required information.

    Mtc22_0-1694028400079.png

    Hopefully it will solve your issue, it did for me.

  • NovemberRyans Profile Picture
    NovemberRyans 2 on at
    Re: Problems using Jira V3

    Hi, I just wanted to drop the real reason this isn't working.

     It's due to the issue type you are trying to use in the Jira side. If the issue has something like assignee on it or data that the connector can't parse, it will error out.

     

    The easiest way to fix this for me was to create a new subtask, remove the elements and then use Jira automation to fix it on the other side...

  • ChaosLasagne Profile Picture
    ChaosLasagne 4 on at
    Re: Problems using Jira V3 | Potential Fix

    I just encountered an almost exact message, with the same outputs that on one board it worked fine and on multiple other boards in the same instance; this message, or at least a very similar message was being encountered.

     

    After some testing, I have managed to fix the problem:

     

    The issue, for me at least, sat within the "Field 'reporter' of type 'user' is not supported.

     

    Essentially, what the difference was between the board that worked and all the boards that didn't was that we had set up the 'Reporter' filed to "Show as blank" is nothing was filled in as standard.

     

    This means if you're using Power Automate to automatically create a ticket within a board, it tries to fill in the 'reporter' field, but can't because by definition, it is blank therefore it is hidden, which causes an infinite loop.

     

    The fix, remove the validation and have the 'reporter' field always show.

     

    Once we did this, every single board worked as expected.

     

    Hope this helps!

  • cchen27 Profile Picture
    cchen27 4 on at
    Re: Problems using Jira V3 | Potential Fix

    How did you resolve this @ChaosLasagne?  I'm still seeing the reporter issue on my end. 

  • _romi Profile Picture
    _romi 4 on at
    Re: Problems using Jira V3

    Hello there,

    I cannot make the Reporter and type field not required in the Jira project. Any other workaround for this error?

  • artivo36 Profile Picture
    artivo36 78 on at
    Re: Problems using Jira V3

    Same here. I mean, if you do not provide a parent field how should power automate know which issue is it child / subtask of ?

  • artivo36 Profile Picture
    artivo36 78 on at
    Re: Problems using Jira V3 | Potential Fix

    @ChaosLasagne Can you please provide details of your flow. Apparently you did not run into the "parent" issue. Big question is, how did you mitigate this ?

  • cchen27 Profile Picture
    cchen27 4 on at
    Re: Problems using Jira V3

    I ended up using the HTTP connector to resolve my issue.  Jira connector would not work for me.

  • AL-09081051-0 Profile Picture
    AL-09081051-0 4 on at
    Problems using Jira V3
    I found this post after stumbling into the same problem. I followed instructions provided by @ChaosLasagne and they worked for the most part. I wanted to create an issue on a team-managed project but was getting "Field ____ of type ____ is not supported".
     
    First with a selection field, so I adjusted the issue type to not make that selection field required, then I adjusted the workflow to restrict issue transition unless the selection field was populated.
     
    That resolved my first error, but then I received the same "field reporter of type user is not supported", so this is where @ChaosLasagne solution came in. My issue type was configured to hide the Reporter field if it was empty, so I moved it to always show. Unfortunately, I was STILL getting the same error, because as others said, the Reporter field is required if added as an issue type field and you can't make unrequired from standard config screens.
     
    In my specific situation, I did not need the reporter field for this project or these tickets so I removed the field altogether from the issue type. That finally fixed the error for me!
     
    So if you don't need the reporter field for your particular project/issue type, then I suggest just removing it entirely.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Tom Macfarlan – Community Spotlight

We are honored to recognize Tom Macfarlan as our Community Spotlight for October…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

Last 30 days Overall leaderboard

Featured topics

Product updates

Microsoft Power Platform Community release plans