i need to grant anonymous access to our jira project, with read-only permissions.
I granted the Browse Project Permission to the group 'anyone' in the project schema, but doing that anonymous users can also change issue status (To do, In progress, Done, ...).
Is there a way to give a real read-only access to a project ?
you'll need to modify permissions to do so.
add jira-user group to "Browse Project" permission. (i think it is by default)
you can also use Roles.
make sure you have your read-only users in this group/role only.
allow working steps like assign, assingable...to f.e. Developers(Role) only.
this will prevent users that are not assigned to the developer role for this project to start the progress
cause by default i think "Start Progress" has the "assignee only" condition.
check permission schemes for more details.
by setting up project roles you can easily define which of your users should be able to see and wich to be able to work on issues
i forgot to add...you also could check the workflow and modify validation of steps.
let me know how it goes
We had a similar challenge, in that we had our permissions set such that "anyone" (i.e. anonymous users) could browse projects, but only regular / logged in users could edit issues. However, we found that anonymous users could still move something to in progress (we'd previously removed the condition allowing only the assignee to execute the "Start Progress" transition). Based on Dario's comment (thanks Dario), we're looking at adding a condition to our transitions, to limit to those with "Edit Issues" permission. Let me know if anyone has any better suggestions.
We have the same issue. We've granted browse permissions to "anyone", but they are also able to change the status of items by clicking on the button on the issue page (See "Open" and "InProgress" buttons below). We're using a GreenHopper Simplified Workflow and have added transitions with contstraints and validators to each transition, each of which (I assume) should prevent a user that is not logged in from moving an item from one state to the next. However, anonymous users are still able to change the state (move from "Open" <--> "InProgress" <--> "Resolved"). We must be missing something obvious, but I don't see it. Any ideas?
Terry - what condition (or conditions) do you have set up on your "In Progress" transition? Our workflow transition's condition (after we changed it) now says "Only users with Edit Issues permission can execute this transition" (although we're not using the Simplified workflow, so our situation may be slightly different).
Thanks for the quick response Andrew. It appears that we're using the same condition, but it didn't seem to make a difference for us. To be clear, "Open" and "InProgress" and "Resolved" (listed under the "workflow" dropdown) are workflow steps, not transitions. Ideally, I'd like to simply just hide the steps and only show the transitions up there. That would solve our issue.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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