Bonfire Permissions - why "Assignable User"?

[Natalie Hobson]

This is not necessarily an improvement request, but a general question - why does Bonfire utizile the "Assignable User" permission to allow users to join a shared test session and enter issues? Wouldn't it make more sense to use the "Create Issues" permission? See documentation:

https://confluence.atlassian.com/display/BONFIRE/Working+with+Sessions#WorkingwithSessions-CollaboratingwithsharedSessions

Text in blue window ("To join a shared test session...").

[edwin · Accepted solution]

Hi Nat,

Great question. Without adding the complexity of a whole new set of permissions for Bonfire, we looked to use JIRA's permission in a way that made sense.

When we looked at who can join a session, we looked at it from the point of view of who can be "assigned" a session, more so than creating issues, because at the heart of it, a participant in a session can do almost all that an assigned can do.

Thinking about the typical scenario of a development project, then participation of testing sessions whould really be kept to those who can "work on" that project - mostly the developers and QA. Looking at permissions, the "assignable user" most closely reflected this - "assignable users" are users who can "work on" issues.

Issue creators on the other hand typcially encompasses a wider group of contributers (e.g. other users in the organisation, or external customers if your issue tracker is public), which are not as close a fit.

Of course, not every deployment is the same, so this may not always be the case. Do you have a scenario where it makes more sense for the permission to use "Create Issue"?

[Natalie Hobson]

Well, to me it does make sense that the user assigned the session have the "Assignable User" permission, but I still think that "Create Issue" better fits those who are only joining the session. In a common scenario for my company, the users joining a test session to log issues would be QA and maybe some customer support people checking out a new game; they definitely wouldn't be developers (users who would end up working on those issues).

In any case, thanks for the explanation! :)