How to make JIRA Read-Only through Database.?

Hi,

Is there any way to make JIRA read-only from database(mysql) end.

Know how to do it by changing permission scheme from JIRA administration. But, looking for a way to achieve this through database side.

Thanks...

Ram

1 answer

1 vote

Not really.  The way you'd do it is actually to just take the changes you've made in the UI, work out how they are held in the database and change it via SQL (while JIRA is offline).  It's quicker to do it in the UI mostly.

Thanks for the response Nic. Can we achieve it through cron jobs.? i.e. without manual effort.!!!

You'll need a cron that can stop JIRA, run some SQL against your database, and then restart JIRA. And you will need to be very careful with the SQL - it will need to read the current settings and store them somewhere so it can put them back when it's done (remember that your admins can easily change the permissions in th UI and you need to preserve what they're doing) This makes me question what you're trying to do. If you genuinely need to lock JIRA out for a while for a good reason, then it's probably going to be far more simple to just stop it.

My scenario is like we have two JIRA instances. One(JIRA1) go live and one(JIRA2) backing the Live instance. If our Live instance(JIRA1) down for some reason we would like to point to backup JIRA(JIRA2) which should be in read only mode with all the latest data of Live(JIRA1). Where users can only view all issues until LiveJIRA (JIRA1) is up. Hope this briefs my concern :).

Ok, that makes sense, and keeps the SQL simple - keep a single permission scheme which says "Browse: all users" and no other rights, and apply it to all of the projects in the "read only" version.

The problem though is that just takes care of Project data. If you've got plugins installed they might have different permissions ways. Also JIRA interacts with the database (in a write fashion) when folks are just logging in or viewing things... There are also crons etc. Just things to be aware off...

Yes, and for JIRA to even start up, it has to have *write* access to the database. In this case, I'm not sure you care too much about it, as I assume that the aim is just to stop updates until the production server is back up (because otherwise people might update it and then complain about data loss), and when production is back, you're going to throw away the disaster recovery system and rebuild it from production again.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,321 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot