-
Bug
-
Resolution: Fixed
-
Low
-
3.10.0, 3.10.1, 3.10.2, 3.10.3, 3.11.0, 3.11.1, 3.11.2, 3.12.0, 3.12.1
-
None
-
Severity 3 - Minor
-
3
-
Note that multiple projects could be affected by this issue, so you might have to apply the same workaround to multiple projects:
Ensure to make a backup of DB before making any changes to it.
Shutdown JIRA.
Run the following query in the database to determine if there is any duplicate rows corresponding to the warning message:
select * from "AO_54307E_CAPABILITY" where "CAPABILITY_NAME" like 'CUSTOMER_INVITE_EMAIL_SUPPRESSED%';
Let's assume that you got duplicate rows for a given pservice desk ID, as shown in the screenshot below (in this case, the project ID is 1):
The resolution consists in removing all the duplicate rows with the highest ID. In the example below, there are 2 duplicate rows for the service desk id 1 with the IDs 52 and 53, so the 2 rows below need to be deleted. If you see duplicate rows for other projects, please delete them as well. Note that the query below only applies to the example provided above. The IDs will likely be different in your instance.
delete from "AO_54307E_CAPABILITY" where "ID" = '52' delete from "AO_54307E_CAPABILITY" where "ID" = '53'
Start up JIRA and verify.
i'm having a problem where the "do not send account verification emails" toggle will not stay checked "green"
as it stands, this means i can't actually disable the invite confirmation emails
we're running an eval of Jira software and core 7.7.2, and service desk 3.10.2, currently just on the h2 db
if i pull up google chrome's javascript console and click the toggle, the following is shown:
POST [https://jira.MY.FQDN/rest/servicedesk/notifications/1/customerinvite/34|https://jira.my.fqdn/rest/servicedesk/notifications/1/customerinvite/34] 409 () (anonymous) XMLHttpRequest.send @ batch.js?agile_globa…erational=true:7006 send @ batch.js:200 ajax @ batch.js:194 value @ context-sd.admin.out…6.js?locale=en-US:1 value @ context-sd.admin.out…6.js?locale=en-US:1 update @ context-sd.admin.out…6.js?locale=en-US:1 value @ context-sd.admin.out…6.js?locale=en-US:1 change #js-suppress-customer-invite-email @ context-sd.admin.out…6.js?locale=en-US:1 dispatch @ batch.js:107 h @ batch.js:99 Uncaught TypeError: t.forEach is not a function at Object.<anonymous> (context-sd.admin.out…6.js?locale=en-US:1) at j (batch.js:63) at Object.fireWith (batch.js:64) at Object.fire [as reject] (batch.js:64) at Object.<anonymous> (context-sd.admin.out…6.js?locale=en-US:1) at j (batch.js:63) at Object.fireWith [as rejectWith] (batch.js:64) at d (batch.js:189) at XMLHttpRequest.b (batch.js:201) has anyone else had this issue or similar?
—
edit: maybe i should note, this is running behind nginx for https
- relates to
-
-
- Closed
-
-
JSDSERVER-1708 Provide ability to disable the welcome email to new customers
- Closed
- is duplicated by
-
![[JIRA Server (Bulldog)]](/images/icons/generic_link_16.png "[JIRA Server (Bulldog)]")
JSDS-1841
You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-5713] Error when disabling account creation emails
@elisiario.f.couto, I'm also on those versions. I opened a ticket with Atlasssian support but it doesn't seem they are aware of this bug where it randomly turns back off. I'd suggest if you are having this problem as well to open a ticket with them.
We have the same issue and we are running Service Desk 3.14 and Jira Core 7.11.
Sometimes we have duplicates in the database and every time we open the settings page with the toggle, the ID is incremented on the database.
Does anyone has this problem with this set of versions?
this is still not fixed. The workaround provided here works at first but then duplicates are generated again. Any updates on this?
Anyone only find one instance of the row? I didn't get any duplicates as shown in the workaround yet the button keeps getting turned off randomly.
the above db queries in the issue description have resolved the "unsettable switch" errors we were having, as mentioned originally in https://jira.atlassian.com/browse/JSDSERVER-1708?focusedCommentId=1732238&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1732238
thanks @lgoodhewcook !
We have this same issue in one of our SD-project, but in our older projects the setting is staying off. Running Server JIRA Service Desk 3.11.0.
This is really annoying and because of this we have to explain the account verification mail in our issue created-notification, that doesn't really give an expert customer service feeling to the customer...
We have been having the same issue as well, and it's been preventing us from testing Jira as a helpdesk tool.
I have exactly the same issue. JCore 7.8.1, JSD 3.11.1, Apache 2.4.18, Firefox 56.0.2. A quick fix would be appreciated.
There is a follow up ticket here https://jira.atlassian.com/browse/JSDSERVER-5972 if you could add your votes and feedback there it would help a lot.