Is it possible to setup JIRA in the following way:
JIRA lets people see issues based on their permissions and security. Permissions work at a project level, so at the most basic access is "a read only user is someone who has only 'browse project' permission". That lets them see all the issues in the project though.
To protect indidivual issues, you can set a security level that limits the visibility. So your "can only see issues from an admin query", can't technically be done, but you can set it up so that a set of security levels hide issues. The read-only user will only see issues that you do not set a level on, or you include them in the level's rules.
On fields, it's a no because JIRA is for collaboration, so generally people want to be able to see all the information. You can restrict comments to groups, but that's about it off-the-shelf. You'll need add-ons to hide other fields - I think Tempo has some control over worklogs, but the one I'd reach for is Quisapps field security add-on, as it can control access to most fields.
No problem. There was one other thought I had, as I've done it with another system.
If these "read only" users are not really going to be active JIRA users, you could drop them into another system. We set up a really simple scrape process - a shell script that
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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