-
Bug
-
Resolution: Fixed
-
Low
-
3.14.0, 3.14.2
-
None
-
5
-
Severity 2 - Major
-
3
-
Description
- Seems like a reoccurrence of https://jira.atlassian.com/browse/JSDSERVER-5713
- The toggle option to "not send" notification does not stay toggled if the "Customer Notification" page is accessed multiple times in quick succession (within 2 or 3 seconds).
Steps to reproduce
- Install JSD 3.14.2.
- Create a project.
- Navigate to Customer Notifications UI page screenshot-1.png
. - Toggle the option to "not send" notification.
- Navigate to another page such as "Satisfaction Settings" screenshot-2.png
- Return to the Customer Notifications UI page screenshot-3.png. The toggle is now off. There would be a duplicate row in the DB screenshot-4.png when querying
select * from "AO_54307E_CAPABILITY" where "CAPABILITY_NAME" like 'CUSTOMER_INVITE_EMAIL_SUPPRESSED%';
- Do step 3, 4 and 5 quickly within 3 seconds.
- is related to
-
-
- Closed
-
![[JIRA Server (Bulldog)]](/images/icons/generic_link_16.png "[JIRA Server (Bulldog)]"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-5972] Account verification email cannot be disabled.
Hey all sorry for not quite sorting out the bug in the last ticket (https://jira.atlassian.com/browse/JSDSERVER-5713). The problem is only caused by reloading the page so while you wait for the fix it would be best to avoid loading that page at all. Even to check if the setting is set it's safer to use the database queries from the description
select * from "AO_54307E_CAPABILITY" where "CAPABILITY_NAME" like 'CUSTOMER_INVITE_EMAIL_SUPPRESSED%';
The fix will be available in the upcoming 3.15.2 and 3.16.0 releases
Regards,
Jira Service Desk Team
Same here, SO GLAD someone figured out what triggers it, it was driving me crazy!
For what it's worth, I've been working with support on this and they said you can track the changes to that switch with the following:
"There is a way to track requests to toggle this functionality, and we can use that to see if the setting is being unset through the interface or not. If you go to System -> Logging and profiling, and enable SQL logging, you will see this line added to atlassian-jira-sql.log every time the checkbox is clicked:
2018-08-29 15:26:47,768 http-nio-8080-exec-24 dmadmin 926x623x1 ug5us3 /rest/servicedesk/notifications/1/customerinvite/1 0ms Connection taken. borrowed : 1
"
I tailed that file while visiting the page a couple times really quick and the logs do show up, the switch goes to off, and the database gets a second entry for the customer notification as shown in the workaround here (this workaround doesn't solve the problem, it'll still get switched off if you visit the page too quickly): https://jira.atlassian.com/browse/JSDSERVER-5713
This is also happening to me!! After we toggle the option we cannot visit another page inside the settings as it disables the previous option and no longer allows it to change.
Removing duplicates in DB does not resolve it, we need to restart our instance after removing the duplicates to fix it.
This is very annoying!
Dear Lachan Goodhew-Cook,
Great to hear that these issues will be patched in the upcoming releases.
Can you please provide an indication of when these releases will be rolled out?
Kind regards,
Marc