-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1.0
-
Severity 3 - Minor
Issue Summary
When an issue is being created from Slack integration, if the create screen contains the Account field from Tempo add-on and an account is selected for this field, the create process fails
Steps to Reproduce
- Install Tempo to your Jira instance.
- Add some accounts, teams, users and associate them with test project.
- Go to the test project configuration and enable Tempo there.
- Add Tempo Account field to issue creation screen.
- Create issue with “/jira create” command from Slack and select some account in Account field.
Expected Results
issue created
Actual Results
An error is shown during the issue:
io.tempo.jira__account: Can not deserialize instance of java.lang.Long out of START_OBJECT token at [Source: N/A; line: -1, column: -1]
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[API-433] Creating issue with Jira Cloud for Slack fails if adding value to the Account field from Tempo add-on
The issue has just happened to me as well, it's annoying as hell as we're using both Tempo and Slack integration quite extensively.
I get the same issue.
Also, I cannot use the "leave it blank" suggestion as Tempo has this field configured as "required". I don't think you can change that. We even have a default Account configured for our project and it still won't let you leave it blank (you can leave it blank in Jira directly and it will create the issue with the default Account).
[I don't have permission to attach files, but nonetheless if you leave it blank it is highlighted red and says "Please complete this required field." below it.]
This is a very frustrating issue. I plan to aggressively move to get my company to stop using Tempo as result of this. We can create Issues via the Microsoft Teams integration at this time with no error.
Any update there?
We currently use Tempo Team & Account and we cannot leave it blank. Those fields are set by reporter during creation.
I recommend Jira Cloud for slack to review the code and fix the API request as it is probably connected with providing correct JSON format similar to this: https://community.developer.atlassian.com/t/tempo-error-when-trying-to-create-issue-via-the-jira-cloud-rest-api/28074