Project

General

Profile

Bug #6705

Session admin definition.

Added by Julio Montoya almost 8 years ago. Updated about 7 years ago.

Status:
Needs more info
Priority:
Normal
Assignee:
Category:
Sessions
Target version:
Start date:
16/09/2013
Due date:
% Done:

10%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

The session admin is defined by the "session.session_admin_id" field but now I just found that he can also have a relation with the session in the table 'session_rel_user' like the RRHH role.

session_rel_user.user_id =  x and session_rel_user.relation_type = SESSION_RELATION_TYPE_RRHH (1)

This means that we don't need anymore the session.session_admin_id field and also that a session can have multiple session admins.

There's a bug in 196 that the session admin can't see his sessions. See https://task.beeznest.com/issues/6707

History

#1

Updated by Yannick Warnier about 7 years ago

  • Category set to Sessions
  • Status changed from New to Needs more info
  • Assignee set to Julio Montoya
  • Target version changed from 1.9.8 to 2.0
  • % Done changed from 0 to 10

I don't think this is right.
The session.session_admin_id is the session admin responsible for the creation (or management) of the session.
The session_rel_user relationship, however, is what allows a session admin to act as a DRH and "track" the session's progress.

In the first case, the session admin can delete and change the session.
In the second case, the session admin can only see the progress and some other data about the session (he cannot change it, unless he is also in case 1).

But I do agree that this could be clearer.

Knowing all that, would you like to suggest anything specific?

I'm moving this to 1.10 (I don't think we have to find a solution for 1.9.8), but feel free to change that.

Also available in: Atom PDF