Install
Nullify uses Atlassian Forge for Jira integration. Jira Connect descriptors and developer-mode installation are retired; do not use an old Connect installation URL.
The shared Jira, Confluence and Compass setup is being prepared for Marketplace distribution. Availability depends on the production deployment and Atlassian approval. The existing Marketplace entry is private; an unpublished draft is not a customer installation destination. Nullify uses enterprise pricing under your existing agreement.
Set up the shared app when available
Open Settings → Connectors → Atlassian in Nullify, or choose Atlassian during onboarding. The legacy dashboard opens the shared settings in another tab.
Enter your Atlassian site URL and authorize the site as a Jira administrator. Authorization associates the site with your Nullify tenant; installing the Forge app is a separate action.
Use Install app when the deployment provides an approved Atlassian installation destination. If installation is unavailable, contact your Nullify representative; do not substitute another app or a Connect descriptor.
Approve the permissions shown by Atlassian. Jira is required; Confluence and Compass are optional contexts on the same site.
Return to Nullify and check installation status. Enable the integrations you need. For Confluence, select the numeric IDs of the spaces whose security documentation Nullify may read.
Jira declares its issue and comment subscriptions in the Forge manifest. No manually configured Jira webhook is required. Product settings control Jira processing and Confluence reads separately. Compass ownership ingestion into the shared router app is still being completed. DX connects independently using an organisation token; it is not installed through Forge.
Issue type
By default, Nullify creates tickets using the Task issue type. Select a different issue type in the Jira configuration if needed; it must exist in the target project. See Configuration.
Last updated