Open julyclyde opened 9 years ago
Is anyone responsible for this?
@julyclyde We (Sentry) haven't had time to verify this fix, which is why we didn't get around to merging it. It definitely looks good at a glance, but we're trying to be a bit more strict about stability on our integrations.
This seems to be a problem still. We just added the due date field as a required field on some of our projects but we cant use the sentry integration to open any tickets because the "Operation value must be a string" error is still happening.
Is there any progress on an issue? We are using Sentry 9.0.0 and Jira 7.13.9
@ojomio this plugin is mostly unmaintained. The organization level integration in the main sentry repository is where the sentry team is putting any future effort.
@markstory, does it mean community version will never get it fixed?
@ojomio The jira integration works in on-premise as well.
old fashion would post duedate field as "duedate": {"id": "2015-07-31"} but Jira refused it: "Operation value must be a string" this commit fix the formatting. Tested on Jira 6.4.4