Versions Compared

Old Version 6

changes.mady.by.user Björn Brynjar Jónsson

Saved on

compared with

New Version Current

changes.mady.by.user Björn Brynjar Jónsson

Saved on

Key

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

When Smart Guess is first installed users need to grant the solution the following access:

...

Where the heading says:

“Smart Guess for Sprint Planning would like to access your Atlassian account”

What permissions does Smart Guess require and why?

The following table describes the permissions Smart Guess requires and why they are needed:

Required permissions

Why is it needed?

Exchange data with the following url:

  • api.smartguess.is

Smart Guess Realtime Engine shares key user actions with team members taking part in the estimation when it happens.

This is critical so that all team members can see who has joined, who has given an estimate, etc.

The Realtime Engine doesn't process or store personal data, in line with the GDPR principle of ‘purpose limitation.’

Retrieve images used by the Atlassian libraries through the following urls:

These permissions prevent the app from reloading when retrieving images from these sources.

Smart Guess is using Atlassian Libraries that retrieve images from these sources. They provide automatically generated avatar images when user-provided images are missing, issue type images and so on.

View Jira issue data.

Allows Smart Guess to read the issue key

in order

to retrieve the current state of the planning session for the issue. Furthermore, retrieve the current story point value to show users if story points

needs

need saving.

View user profiles

Used

It is used to identify who has joined the planning session

,

and who has given an estimate and to retrieve

users name, profile picture

the user's name and profile pictures displayed to other users.

Notice that Smart Guess does not store any personal data. Only retrieves it on demand, in line with the GDPR principle of 'data minimization.'

Create and manage issues.

Allows Smart Guess to:

  1. check if the story point field can be updated

  2. save the story point value selected

View user profile

Used to retrieve the following information about the currently logged-in user:

  1. has the user already joined the planning session

  2. current estimate

App storage scope

Allows Smart Guess to store

current state of

the planning session's current state for the

current

issue. In other words

;

, what users have joined and their estimates.

No

Notice that Smart Guess does not store any personal data

is stored by Smart Guess. Only references to Jira user accounts.

Share data with domain: api.smartguess.is

Service allowing key user actions to be shared with users who have joined the planning session. Critical so that the team can view the team estimates at the same time, see who has joined and given an estimate - when it happens

. Only retrieves it on demand, in line with the GDPR principle of data minimization.

Write Jira User Property

Used to track if the current user has already seen

  1. user onboarding messages

  2. new release messages

So that these messages are only displayed once for each user.

Write Jira Field

Used to keep the following information up to date:

  • Estimated by - who has estimated the issue

  • T-shirt estimate

Manage Jira Configuration

Allows users to save Story Point estimates without having to edit Jira configuration for every project your teams are using. Without this permission Jira Admins had to associate Story Point field to the appropriate screen for every project.