Permissions Smart Guess requires

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 compliance with GDPR ‘purpose limitation’
api.openai.com generativelanguage.googleapis.com api.anthropic.com	Smart Guess Coach leverages the following APIs to analyze your team's performance data and generate actionable insights. The system shares only: Performance metrics: Aggregated statistics such as cycle time, throughput, and WIP limits Issue references: Keys like ISU-123 to pinpoint specific bottlenecks or problems Workflow states and transitions The Coach doesn't process or store personal data, in compliance with GDPR ‘purpose limitation.’
View Jira issue data	Allows Smart Guess to read the issue key to retrieve the current state of the planning session for the issue. Furthermore, retrieve the current story point value, estimated by value, t-shirt estimate value.
View user profiles	Used to identify who has joined the planning session and who has given an estimate and to retrieve 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 compliance with GDPR 'data minimisation.'
Create and manage issues.	Allows Smart Guess to: check if the story point field can be updated save the story point value selected
App storage scope	Allows Smart Guess to store the planning session's current state for the issue. In other words, what users have joined and their estimates. Notice that Smart Guess does not store any personal data. Only retrieves it on demand, in compliance with GDPR 'data minimisation.'
Write Jira User Property	Used to track if the current user has already seen user onboarding messages 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.