AETERION

    Jira

    Jira integration

    ITSMAvailable

    BRAIAN connects to Jira through REST API v3, OAuth 2.0. Agents can issue read and creation, transition management and comment posting. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.

    What can BRAIAN do?

    SecAgent reads and creates issues, moves them through the workflow transitions a project defines and posts comments that record what was done. Project access is granted per project, never across the whole site.

    CapabilityAgentRead or write
    Issue read and creationSecAgentRead and write
    Transition managementSecAgentWrite
    Comment postingSecAgentWrite
    Project lookupSecAgentRead

    How does it connect?

    Connection method
    REST API v3, OAuth 2.0
    Credential
    An Atlassian OAuth 2.0 app with a refresh token held in the secrets store.

    Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.

    Which permissions are required?

    • read:jira-work / write:jira-workRead and write on issues in the projects explicitly enabled for the integration.

    Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.

    Which processes use it?

    Processes that run on this connection, and the domains they belong to.

    • Data access review

    • Access certification

    How do you revoke access?

    Access is revoked in Jira itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to Jira and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.

    FAQ

    Does BRAIAN store data from Jira?

    BRAIAN reads what a process needs, when it needs it. Records retrieved from Jira are held only for the duration of the process and in the audit trail of the actions taken; Jira remains the system of record.

    What happens if the connection fails mid-process?

    The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.

    Can permissions be scoped per agent?

    Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to Jira.