Is it safe to modify workflow directly in JIRA database?

[Caner Arda]

We are working on an upgrade from JIRA 4.3 to 6.3. We have imported all the data into 6.3 and did significant workflow modifications to resolve the problems with custom groovy scripts etc.

My concern is, when we perform the upgrade on the live system, would it be safe to update the workflows directly in database, after import has completed (JIRA will be down)? Or are we limited to XML import, which will take significant time while configuring new worflow schemes etc?

[Joe Pitt · Accepted solution]

NO. You're asking for trouble to do anything directly in the database except read operations.

[Caner Arda]

Thanks for the answer. From your experience, how would you tackle the problem?

[Joe Pitt]

To be safe you need to go through the same steps as the first time. This is the primary reason I don't do any customization and only use supported plugins. You lose much of the advantage of a COTS product when you heavily customize it. When responding to requests you need to ask if this is really mission critical or a 'nice to have' or a user training issue. I've seen lots of code written to accommodate users not doing things right. A couple days off without pay can usually take care of user not doing things correct issue after a couple warnings.

[MattS]

I've tweaked workflow XML in the db occasionally when JIRA is stopped. But  it is more error prone so I avoid doing it. If it's just a few workflow schemes you'll have to update I'd do it the right way.