Sometimes when the reporter tries to close an issue on Service Desk standard screen (without comments), the screen doesn't submit the form and it doesn't shows any error message.
The "close" transition doesn't have any validation in the workflow.
Hey @Marcos Sciarra
Could you provide some screenshots?
Is the reporter closing the ticket directly from the Portal?
The screen is the Portal standard screen.
There is not much to say on the screenshot because there is any error message shown on the screen. You hit the submit (accept or close) button and nothing happens.
The behaviour was shown several times on both Chrome and Safari browser (latest version, latest patch).
The problem occurs no matter if you add a comment or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is some "Error 400" on the analysis console.
It is worth to mention that we are running in a SSL conection.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Having this issue too, found anything that solves it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've not found anything yet. Still doing some research when I can.
Which version are you running?
I haven't found any open bugs for this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Running
Jira Software v7.13.0
and
Jira Service Desk v3.16.0
Only seems to be happening to our old issues in my instance's case, from before our move to Service Desk. At least that's been reported to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are there any automation rules in the project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are. Just tried turning them off and running the close command, still does the same thing though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried on our instance, we are running a lower version of both JSW and JSD.
7.11.2 JSW
3.14.2 JSD
I was not able to reproduce the error.
I would suggest opening a ticket with Atlassian Support.
They might be able to provide more insight on the matter.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.