Architecture

The application is built entirely on the Atlassian Forge platform. It leverages various native platform modules, including Key-Value (KV) Store for data persistence, alongside frontend modules rendered directly within the Jira customer portal.

Connecting Multiple Jira Instances

UniPortal operates without a remote backend to process inter-instance communication. Instead, the architecture relies entirely on Atlassian’s native 3LO (Three-Legged OAuth) framework (read more) to establish secure, direct communication pipelines between multiple Jira instances based on customer requirements.

The configuration workflow requires authorizing each target Jira instance using a dedicated technical user, which must be identical across all connected environments. This authorization is performed once per instance:

• Master Instance: The initial instance where authorization is completed is designated as the “Master” environment. This instance unlocks advanced administrative capabilities described in section Create Layout of this documentation.
• Secondary Instances: Subsequent authorized environments function as nodes to securely fetch and aggregate data

Third-Party Platform Integrations

For external integrations such as Salesforce and Azure DevOps, authentication is managed locally. A separate configuration must be executed on each individual Jira instance in accordance with the supported authentication methods:

• Azure DevOps: Authenticates via Personal Access Tokens (PAT)
• Salesforce: Authenticates by configuring a dedicated OAuth client