We recently added a field that is required across all projects in our Jira environment. It seems to have broken our ability to create issues from Teams and Outlook with the Jira Cloud add ons because the field does not show. Is there a way to edit the screen scheme that these add ons use in order to add that field?
The Microsoft Teams integration creates issues via the Jira Cloud REST API. Jira enforces required fields at the field configuration level through API validation. The Teams create dialog is a simplified integration UI and does not dynamically inherit project screen schemes. Therefore, if a field is globally required but not exposed in the Teams UI, the API call fails validation.
This is consistent with Jira Cloud API behavior and integration design, and not a defect in the project configuration.
I think there is no possibility of adding more fields there.
Ah, understood. Thanks for the insight, I appreciate the answer!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Noelle Bareswilt
Noelle yeah, that’s basically a limitation of the Jira Cloud add-ons for Teams/Outlook.
Those create dialogs don’t behave like the Jira web “Create” screen. You can’t edit a screen scheme for the add-on, and the add-on doesn’t reliably show all custom fields. So if you make a field required everywhere and the add-on can’t display it, issue creation from Teams/Outlook will fail because Jira is enforcing “required”, but the add-on can’t collect the value.
What usually works as a workaround:
Don’t enforce it as “required on create” globally. Instead enforce it later (workflow validator) or via process.
Give it a sensible default value so creation doesn’t break.
Or use automation to populate it right after the issue is created (based on project/issue type).
Worst case: users create via the browser when they need to fill that field.
So short answer: there isn’t a separate screen scheme for Teams/Outlook you can configure and you’ll need to adjust how that required field is enforced.
I wish you a great Day 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm. The default value would be different based on the team so I'll have to look into what we can do with automation. Thanks, I really appreciate the answer!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You´re Welcome. If you need Help, don´t hesitate to reach out to us :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.