IF you need to add read-only users to project X.
1. Create "Read only users" role. Add needed users there in project X.
2. Assign Browse project permission to "Read only users" role in permission scheme used by project X.
3. Edit all workflows for project X. In every transition add condition "Permission condition" with value "Edit issues".
4. Publish workflows.
By "external viewers", do you mean "anonymous"? The users do not need to log in to see issues in the project?
If so, then go into the permission scheme for that project and add the group called "anyone" to the "browse" permission. Then people will not need to log in to read the issues in projects using that scheme.
I *very strongly* recommend that you do NOT allow "anyone" to have any permissions that allow any form of update because the changes will be done anonymously and that's a total nightmare - the log shows "anonymous" for any changes, so you'll never know who broke what.
Thank you and no, that's doesn't sounds like a good way to do it.
I thought, maybe there was a combination of checkboxes in permission schemes or something like that where you could set a group of persons to just only viewing the issues in the projects. So, access to the project and viewing and nothing else.
So, I'm still wondering if it's possible :-)
I'm still not entirely sure what you're trying to acheive though. Anonymous access? Or certain users only able to read projects, with others able to do more
If it's the second, then yes, you can do it. You just need to edit your permission schemes and role membership so that the default access is "read only" and then you grant more power to people who actually need it (via roles ideally, as it's more flexible than groups)
No problem, it's quite hard to explain computers sometimes - I find paraphrasing very helpful when I'm exploring what people might mean, but even then I completely misunderstand what people are saying sometimes.
I can't really really step you through this process because it depedns on what you have configured already. I've kind of pointed you at what needs doing at a high level already, and I can't tell you more without knowing your setup.
However, when I take over Jira installations that need this type of thing, what I do is:
This separates "can log in" from "can do all sorts of other stuff in assorted projects"
In your case, I'd also consider
(The slightly easier way to do this is actually to create a new group called something like "jira active users" or "jira logins", put everyone in it, then remove "jira users" from the global "can log in" permission)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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