Wake Scope Justifications

read:jira-work

Wake needs Jira read access to:

• list saved filters visible to the current user;
• read the selected filter’s JQL and metadata;
• read Jira field names and schemas;
• search for issues matching the selected filter;
• read configured fields and small helper fields needed for the table, groups, links, and charts; and
• calculate counts, sums, and averages in the app.

Wake uses asUser, so Jira applies the current user’s permissions.

storage:app

Current code contains setFrameConfig and getFrameConfig handlers for a single FRAME_CONFIG KVS key. No active caller was found in current main after the single-Custom-UI architecture change.

Release recommendation: remove the unused handlers and this scope after checking older installations and migration needs.

If the scope is retained, replace this section with:

• the exact record schema;
• whether it is installation-, dashboard-, gadget-, or user-scoped;
• every code path that can write it;
• retention and uninstall behavior; and
• the customer deletion process.

No scope should remain solely because an older version once needed it.