After a lengthy JIRA tip, I’m about to blog a Keyboard Ninja tip for users who do a lot of Ctrl + R thingy to navigate Bash history.
JIRA to JIRA project migration — most of the time this has been a headache when it comes to customer negotiations and compromises.
So, this is loosely another part of the unofficial series ‘fixing a corrupted JIRA db‘.
However, this is a different case. This JIRA instance (7.1.x) was created by importing a huge XML backup (> 1 million issues). Due to an unknown reason, ActiveObjects didn’t import. That means, JIRA Software (aka JIRA Agile) no longer functioned normal.
Yesterday I blogged about how to fix JIRA Permission Schemes of a corrupted JIRA database. The observation was from atlassian-jira.log, but in my case I soon found out the problem was much greater in my case.
Edit (24 May): Spoiler alert! There’s a better way.
I came across a corrupted JIRA database with all projects lost their permission schemes.
I am a motorcycle rider who encountered with a number motorcycle accidents and still in one piece.
Once installed their app, Facebook thinks they own our mobile devices.
At first, there was the peaceful all-purpose Facebook app. And some time later they separated messaging into another app, creating the Messenger. Initially it was at user’s discretion to use Messenger or Facebook app for messaging. Initially it looked polite but lately everyone was gradually forced to install Messenger. Another app… sigh! Personally, for me messaging is just messaging. I don’t want a childlike fairyland for just sending and receiving messages.