When we create one issue the ID is set to, e.g. 1000, then the next issue is set to 1164 or something like that. This now resulted in having our issues in the hundreds of thousands without any reason.
I have already looked into solutions for this but they are all referencing some kind of plugin that we are not using. We are using Timetracker.
How can we address this problem?
How can we reclaim all those lost IDs?
We are using the on-prem version of JIRA.
I have Google SMTP set for outgoing emails.
Are you talking about notifications sent to users?
I also have email handlers for creating issues from emails sent to our jira inbox but never seen any failing to process. All of the emails sent to that account are turned into issues. How can I find out if there are emails that aren't going through?
Also, I only see this in one project, even though I have 2 projects.
The problem I've seen is purely with incoming email. Your "if I create quickly" note is in-line with the incoming email problem, as the emails are scanned periodically, so you are creating between scans, while no rogue issues are being created.
The easiest check you can do is to turn off your mail handlers for a while and see if the problem stops (they'll pick up where they left off when re-enabled)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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