+4
Answered

What rights has which role?

Kapitain Nemo 10 year бұрын updated by robin 8 year бұрын 5
I do not see what the role's differences are - without trying myself ...
Cant find any simple documentation of this either
Under review
We'll add a page for this on the site, and there is very little differences between the account types for now, but here's the basic info:

- Account Manager: Has all permissions, manages the organization, the users, everything. He's the king!
- Project Manager: Can manage every aspect related to one project. He can invite users, archive projects, delete any bugs, change the status of any bug, etc.
- Developer: Can report bugs and update bugs, delete his own bugs, but not other people's bugs.
- Tester: Can report bugs, update bugs and delete his own bugs, but not other people's bugs (same as "Developer".)
- Client: Can report bugs, update bugs and delete his own bugs, but not other people's bugs (same as "Developer".)

At the moment, Developer, Tester and Client are very similar because we couldn't think of any reason why there should be significant differences in permissions between all. Maybe we'll add a read-only Client role if there's enough demand, and we are open to making changes if you have other needs.

+2
For the last 3 kind of roles would be very useful to define different visibility rights on bugs. I try to explain me better:
  • Developer: he can see all the bugs
  • Tester: I mean that this kind of user is inside the organisation and so I can think that he is able to see all the bug, but may be only the open ones.
  • Client: this kind of user is outside the company and so I would prefer that he is able to see ONLY his bugs or some specific bugs that the admin (or the product manager) signs as "public"
At your disposal for further information

Older

I agree. For a previous bug tracking software that we used, we had ability to flag a bug as internal or external (defaulted based on user profile) and internal users could see all bugs, external users could only see external bugs. This prevents clients from seeing bugs that were resolved before the version of the app that they started testing/using.