[🐛 Bug]: Create issue on jira if priority is not present

[thibautmery]

Describe the bug

I connected Jira to Keep, but the problem is that in my ticket creation form, I don't have a “priority” field. The provider's code necessarily provides one (set to “none” by default).

{'priority': "Field 'priority' cannot be set. It is not on the appropriate screen, or unknown."}}

To Reproduce
Remove priority from ticket workflow

Expected behavior

If I need priority, I have to set it up.

[dosubot]

This error happens because the Keep Jira provider always tries to set the 'priority' field if it's included in your workflow, but it doesn't check if that field is actually present on your Jira ticket creation screen. If Jira doesn't recognize the field (because it's not on the screen or not configured for that issue type/project), the API call fails with the error you saw "Field 'priority' cannot be set. It is not on the appropriate screen, or unknown.".

To avoid this, make sure your Keep workflow or integration does not include the 'priority' field in the custom_fields or action parameters if it's not present in Jira. There’s currently no built-in logic in Keep to automatically detect or omit missing fields—this needs to be handled in your workflow definition. If you want to use 'priority', add it to your Jira screen; if not, remove it from your Keep config.

Let me know if you want help editing your workflow YAML or have questions about your setup.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[thibautmery]

@dosu The problem here is that in the provider code on Keep, we enforce a value for “priority.” The issue is that even if I remove it from my workflow, it will still be pushed by Keep at the end. This will cause an error because Jira does not expect a “priority” field.

[dosubot]

The Keep Jira provider does not enforce or inject a 'priority' field unless it is explicitly included in your workflow's custom_fields or action parameters. If 'priority' is not present in your workflow config, it will not be sent to Jira, and you should not see this error. The provider simply merges whatever fields you supply—there is no hardcoded or default 'priority' field in the codebase¹.

If you're still seeing 'priority' sent, it's likely being added by a template, automation, or inherited config elsewhere in your setup. Double-check your workflow YAML and any shared configs for a 'priority' entry. If you want, you can share a sample workflow and I can help spot where it might be coming from.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

Footnotes

1. Jira provider code reference ↩

[qaoru]

@dosu The "priority" field is enforced on the jira on-prem provider though which is problematic