Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt


Info
titleAgile Poker Cloud

This part of the documentation relates to Agile Poker for Jira Cloud. If you use Jira Server go to the Agile Poker for Jira Server and Data Center documentation.


Session Types

Each estimation session (Interactive, Asynchronous, Relative or Bucket Sizing) can be created as either Public or Private:

  • Public - unrestricted session access. Every Jira Software user can access such session, update its configuration and participants list (including moderator, participants and observers roles). All Jira restrictions apply here: users who do not have access to the specific project, board or issue will not be able to see restricted data. But they can still join and modify a public estimation session in Agile Poker.
  • Private - restricted session access. Only the users invited to the session (moderator, participant, estimator or observer) can join it.  Depending on the role the user will be able toget:
    • Moderator - full session access, ability to update session participants (add or remove users), update session configuration, change a moderator, finish the session and or remove it;
    • Participants (Participant / Estimator / Observer) - limited session access, ability to participate in estimation process that is controlled by a moderator. Note: Agile Poker allows setting "Everyone" as the moderator that means results in every session participant will get getting moderator's permissions.
    • Jira administrator - remove any active or finished session. Administrators will be are not able to join a private sessions session if they are not on the session's participants list.
Info

Once session is created it's impossible to change its type. We plan enabling session type change in the future, you may watch [APJ-1617] As an AP user I want to switch a running session from Public to Private for the updates.

More on session user roles:

  • Moderator - controls the session flow: picks up the Jira issue(s) to be estimated, enables/disables voting, finishes the session;
  • ParticipantEstimator - participate participates in the estimation session but can't control its flow;
  • Observer (available for Interactive sessions only) - observes the estimation process but can't provide estimates, session is progressed without observer's input.

Once session is finished (estimation is completed; "Finish session" action executed) then it is not longer possible to join it or update its configuration. 

...