Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Ticket numbers jumping

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?

4 answers

1 accepted

3 votes
Answer accepted

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 <f.fix@eventbs.com>]][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

Ahh, well spotted :-)

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.

That would be nice. I had two years of logs filled with three emails it couldn't parse every 10 minutes. Fortunately, none of them were creates, but it would have been nice if it could have just given up and stopped polluting my logs.

I am experiencing exactly the same issue as described here. I use JIRA v7.0.0#70107. The issue is still not resolved. Dear JIRA developers, please let me know if it is planned to resolve the issue and when?

Have the same issue with one of our projects. How do I identify the problematic email on the server and delete?

1 vote

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.

Thanks for your answer. We installed a second instance of jira (with a separate db) to test jira 6. Could it be related to a shared configuration file or such? The databases are definitely separated.

It's unlikely if the two Jiras are separated.

But you have not answered the question that we need an answer to before we can help you much. Is it the database IDs or the issue keys?

The issue is reported here: https://jira.atlassian.com/browse/JRA-22110
The root cause is here, and is on the Atlassian backlog: https://jira.atlassian.com/browse/JRA-35310

Please go and vote there, as it's been an issue for quite a long time now.

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

 

It's probably the same problem as discussed above.

What does your log file say the problem is?  Are there emails it can't delete in the mailbox?

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you