Since today the ticket numbers in our local jira jump to higher values very quickly. We were at ticket id 7000 something and 20 tickets later it was at id 8700. Do you have an idea what the reason for that could be?
It was the issue keys. We found the reason:
An issue that was created by mail could not be saved to the database because of some special characters. However the ID-count was still increased. This is the exception:
[Created via e-mail received from: Frederik Fix <firstname.lastname@example.org>]][priority,3][timeestimate,null][duedate,null][timeoriginalestimate,null][watches,0][key,MP-10070] (SQL Exception while executing the following:INSERT INTO jira issue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESP ENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xE2\x97\x8F ...' for column 'DESCRIPTION' at row 1)) at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:136) at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:101) at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:64) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:487) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:467) at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:98) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:374) ... 21 more
This just happened to us as well (JIRA 6.1.7). Exactly the same log output, but we don't monitor the logs frequently so we "lost" about 5000 issue numbers before realizing it. I ended up having to delete the email off the server to get it to stop. Seems like maybe it should only try a few times before marking the email as un-insertable.
Do you mean the IDs in the database or the actual issue keys (with the project id and sequence in them)
If it's the second, then that would only happen if someone really did create and then move or delete 1680 tickets.
We are seeing the similar issue on our JIRA v7.2.7 Instance.
This problem is only happening under projects where we setup create a ticket via an Incoming Emails. e.g. DEVOPS, IT HelpDesk.
Can someone please update or share any workaround to change any settings under Mail Handlers if any?
I see Atlassian has : https://jira.atlassian.com/browse/JRASERVER-61788
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs