JIRA: Removing old sprints from migrated ticket to resolve a velocity chart issue
Ran into an interesting problem in JIRA that I managed to solve this morning. Figured it might help out others, so here goes!
It turns out that if you had a ticket that was part of a Sprint in one Project, but then either move it to another project or clone it, it'll still retain a history of the prior closed sprints it was in. At first, that doesn't seem like a big deal, but it means that the Project it's now part of will have messed up Velocity Charts, because it'll start including the Sprints from the other Project. And there's no obvious way to remove the old Sprints from the ticket (editing the ticket only lets you change the current Sprint assignment, not clear out prior ones.) No good!
Fortunately, the Bulk Edit feature provides a workaround and will let you clear out the old Sprint associations, which will then fix the Velocity Charts. And here's how to do it:
Run a search that'll return the ticket you need to remove the sprints from.
Choose the "Bulk Change" option from the "three-dot menu" in the upper right.
Check only the ticket you want to change. Hit Next button.
Choose "Edit Issues". Hit Next button.
Check the "Change Sprint" option. Leave it blank. Hit Next button.
Review the Confirmation screen. Hit Confirm button.
Hit Acknowledge button when the progress meter is done.
Microsoft Access Query is Corrupt errors.
Earlier this week, Microsoft released several Security Updates that caused update queries in Microsoft Access database applications and programs storing data in Microsoft Access databases to fail.
An erroneous Query is Corrupt message appears.
Microsoft Access 2010, 2013, 2016, 2019 and Office 365
32 and 64 bit versions of Access
Applications that use the Access Database Engine (ACE) such as those written in Visual Studio .NET, VB6, and even web solutions that update Access databases.
Detailed Article with Multiple Workaround Suggestions
Our customers encountered this confusing error, and our team investigated and published an article to explain the issue and how to mitigate it. Microsoft announced they will fixed this in the next security update in December. That's hardly acceptable for applications that were running perfectly fine on Monday. Hope this helps.