How to make JIRA Readonly ?

[Chaithra N]

In the older JIRA instance 3.12.3, we were making JIRA readonly by enabling only SELECT on the jira db (MYSQL) for the jirauser.

But in 4.4.1, JIRA doesnot not start up if we enable only SELECT on the jira db for the user.

Can anybody please help.

Thanks

[Chaithra N · Accepted solution]

As mentioned in the question, First All privileges for db user was revoked, then only select was enabled for db user for the JIRA DB.

And then granting privileges to few tables (cwd_user_attribute, userhistoryitem etc) helped in JIRA starting & also JIRA is readonly.

[Jacques]

I think it's best to change the permission scheme for all your JIRA projects instead of putting this limitation on your database. If you give your users only the "Browse Project" permission they will only be able to browse projects and issues within them. They won't be able to create, comment or do anything else.

[Chaithra N]

Thanks Jacques,

Even If I have the Permission configured for all the Project, user will still be able to do Workflow Action & the Number of Workflows is more in our instance and each worklow have many tranistion.

And it will be difficult to go to each transtion & have condition which refers to some permisison

DB method was easy & was working fine in 3.12.3, but it is failing in 4.4.1

[Rozita]

Hi Rdolfo,

Thanks for the reply. But it is still from Jira itself and Is hould do it one by one correct? Can I do it from back end and just for example inside mysql configs?

thx

[Rodolfo Romero]

As Jacques mentioned, creating a Permission Scheme that allows only "Browse" to the "jira-user" group will let users navigate through the tickets and projects having this new Permission Scheme setup but it won't let them modify any at all. If you are seeing the users being able to do any other action, it means they belong to the 'jira-administrator' user group.

[Rozita]

Hi,

May I know how I can I try it for the curernt version?

thx

[Chaithra N]

As mentioned in the question, First All privileges for db user was revoked, then only select was enabled for db user for the JIRA DB.

And then granting privileges to few tables (cwd_user_attribute, userhistoryitem etc) helped in JIRA starting & also JIRA is readonly.