Jira

Issues, projects and where work stands. Read-only.

Connects with	Atlassian API token
Reads	5 operations
Writes	None
Irreversible	None
Personal data	Assignees, reporters and issue text.
Data stays in	AWS Sydney (ap-southeast-2)

What it reads

• Issues, searched with JQL and read in full by key.
• The projects the account can see, with their keys.
• Every field, system and custom, so a custom field’s id maps to its name.
• The workflow statuses in use.

StoriBot reads only what the connected account can see in Jira.

What it does not read

Attachments, and anything outside the projects the connected account can see.

What it writes

Nothing. There are no write operations in this connector.

How you connect it

Connect with an Atlassian API token. Create one at id.atlassian.com under Security, then API tokens, for an account with read access to the projects the Stori needs.

What StoriBot will ask for

• Your Jira site name: the first label of the address, so acme for acme.atlassian.net.
• The email address of the Atlassian account the token belongs to.
• The API token.

Every operation

These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.

All 5 operations

Operation	Kind	What it does
search_issues	Read	Search issues with JQL.
get_issue	Read	Retrieve one issue by key or id.
list_projects	Read	List the projects the account can see, with their keys.
list_fields	Read	List every field, system and custom, with its id, name and type.
list_statuses	Read	List the workflow statuses in use, each with its name and category.