Degraded performance Customers may experience issues using Community search. Our team is investigating.
We were looking at a way of bulk closing a large number (1000+) issues via MySQL (changing the issuestatus etc), the issue itself updated fine but when we do a filter or a search for the issue then it hasn't updated.
We have now changed all the colums in the jiraissue table back to their original, but now if I change anything in the issue itself, the filter doesn't reflect the changes (such as changing the assignee, the status, etc etc)
Is there anyway I can completely remove the issue from the system (as it's only a test issue) I tried removing the row from Mysql (jiraissue table) but it removes the issue, but it still shows in the filters and searches.
You should NOT update a Jira instance with SQL unless it is offline, backed up, and you re-index it afterwards (for most changes, some don't need indexing).
Indexing is proportional to the number of issues you have, but strongly influenced by the hardware/resources available as well. A few thousand issues will take a few minutes, but hundreds of thousands is a significant outage. Very broadly, estimate 2000 issues a minute, but that is REALLY rough.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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