Skip to content
This repository was archived by the owner on Aug 28, 2023. It is now read-only.

Conversation

@julyclyde
Copy link

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

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
@julyclyde
Copy link
Author

@julyclyde
Copy link
Author

Is anyone responsible for this?

@dcramer
Copy link
Member

dcramer commented Apr 11, 2016

@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.

@jersak
Copy link

jersak commented Oct 22, 2018

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.

@ojomio
Copy link

ojomio commented Mar 10, 2020

Is there any progress on an issue?
We are using Sentry 9.0.0 and Jira 7.13.9

@markstory
Copy link
Member

@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.

@ojomio
Copy link

ojomio commented Mar 12, 2020

@markstory, does it mean community version will never get it fixed?

@markstory
Copy link
Member

@ojomio The jira integration works in on-premise as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants