Starhive for Jira: what the "Not configured" and access messages mean
The Jira integration shows Starhive data in two places — a Starhive custom field on an issue, and the Starhive tab in a project. Before data loads, either can show one of three messages instead of an error. Most users never see them; they show up only on first use, before an admin has configured a field, or when your Starhive access has changed.
| Message | Meaning | Who resolves it |
|---|---|---|
| "Not configured" | The field isn't set up against Starhive data yet | A Jira Cloud admin |
| "…requires additional access to your account" | You haven't connected to Starhive yet | You |
| "This content is only accessible to a limited number of individuals" | You lack access to this content in Starhive | A Starhive admin, or anyone who already has access |
"Not configured"
The custom field has been added to the issue/request type, but nobody has told it which Starhive workspace, space, and type to read from yet. A Jira Cloud admin needs to configure the field — regular users can't resolve this themselves.
This field/banner renders inside Jira's own issue view, not a standalone Starhive page — not something to mock up from Starhive's frontend code alone without Jira's surrounding chrome.
"…requires additional access to your account"
The wording differs slightly by location ("Starhive requires additional access to your account" on the tab, "This app requires additional access to your account" on a field), but the cause is the same: Starhive data is shown using your own permissions, and you haven't connected your Atlassian account to Starhive yet.
Press Configure access, then:
- Atlassian's consent screen — lists the requested permissions. Every Starhive scope is read-only (objects, spaces, types, workspaces); the integration can't change anything in Starhive on your behalf. Press Continue.
- Starhive sign-in — sign in with your Atlassian account, Google, or email/password.
You're redirected back to Jira, and the field or tab loads.
The consent screen is Atlassian's own OAuth UI, not Starhive's — not something to mock up from Starhive's frontend code.
"This content is only accessible to a limited number of individuals"
You're connected to Starhive, but your account doesn't have access to the workspace or space this particular field points at. Access is checked per field, so other fields you do have access to keep working normally.
Ask a Starhive admin (or anyone who already has access) to invite you to the relevant workspace or space — once you have access, the field displays its value with no further setup.