Teams integration: cannot create issue, fields are not shown in modal

Thank you for the replies -- I just tried it again today and the fields finally loaded. As I am unable to access any error logs in Teams, I sadly can't tell what the issue was, but perhaps it's been solved by Atlassian already if it was a bug.

Hi @MaxKorlaar ,

Have you tried using the web version to see if it happens there as well? Also, are other users/colleagues experiencing the same thing?

If I recall correctly, there are some limitations when it comes to required fields. What I'd recommend is to navigate to field config. (now field scheme) and make everything as non-required/optional to see if that will help 👈
There's a feature request related to it: JRACLOUD-77876: Support for required fields for Jira issue creation in MS Teams 

There's also this troubleshooting article: Troubleshoot Permission Issues in Jira Cloud for Teams Integration that could be useful.

Finally, if this persists, I'd recommend reaching out to Atlassian Support (as you're on a paid plan) to see if they will be able to provide some assistance here. 🎟️

Cheers,
Tobi

Hello @MaxKorlaar , your instinct about the custom field is the right one to test first, and there is a quick way to prove or clear it.

Why the form goes blank rather than erroring. The Teams create modal builds its form from the create screen for the site, space and work type you picked, through the same metadata Jira gives any client. When one field on that screen is something the modal cannot render, the usual behaviour of a client like this is to fail the whole form, not to skip the one field, and you get exactly what you describe: site, space and type select fine, then nothing, no spinner, no error. Native Jira's create dialog can render every field type; the Teams client cannot, and it does not tell you which one it choked on.

The isolation test, ten minutes:

1. Jira settings, Work items, Screens (or Space settings, Screens for that space): open the create screen for that work type and note the fields on it.
2. Remove the custom field you added (or move it to a tab other than the first one) and retry from Teams. If the form renders, that field is the cause, put it back and confirm the form goes blank again, so you know it is not coincidence.
3. If it still fails with the field gone, halve the remaining fields and repeat, the culprit is almost always a field of a type a chat client cannot draw (a multi-level cascade, an app-provided field type, or a field whose options load from another system).

Two more things worth checking before opening a Support ticket:

• Field contexts. A field on the screen whose context does not include that work type or space produces a mismatch between the screen and what the client is allowed to render; Atlassian's KB on fields not appearing on the create screen covers the context and field-configuration checks (fields missing on the create screen).
• App version. Atlassian rewrote the Jira Cloud for Microsoft Teams documentation in late August (integrate Jira Cloud and Microsoft Teams), which usually accompanies an app update. If your Teams admin pins app versions, check whether you are on the current one.

If step 2 names a field, post the field type here and I can say whether there is a way to keep it and still create from Teams (usually by leaving it off the create screen and populating it by an automation rule on creation). If nothing in the test moves it, that is the Support ticket, and the field list from step 1 is what they will ask for first.