Let’s bring it into focus.

Guidance for setup questions, unexpected results, security concerns and privacy requests.

Send a support ticket.

For app questions, billing, privacy requests and security reports. Every field is required.

Used to identify your request. This form sends no email. Use your Jira Cloud site address, without a project path. 10–8,000 characters. Include what happened and what you expected. Never include passwords, API tokens or customer issue content.

Your name, email, site address and report are stored in Nitrosoft®’s Jira support queue. Read the privacy policy before submitting.

Keep the ticket ID shown on the next page. No response-time or resolution SLA is stated.

Help us understand what happened.

Describe the operation, exact error message and reproduction steps. Use synthetic examples where possible; share site or project identifiers only when needed.

  • What did you expect, and what happened instead?
  • Was this a rule, personal subscription or existing-issue backfill?
  • What saved status did you see after refreshing?

Keep sensitive information out.

Do not send passwords, API tokens, credentials, customer issue content or unnecessary personal records. Support correspondence is separate from Forge app storage.

Report a security concern.

Prepare the affected version, operation, impact and safe reproduction steps for a security report. Choose the Security category above. Do not perform destructive testing on another customer’s installation. See our security statement.

Make a privacy request.

Access, correction or erasure requests may require coordination with your site administrator or Atlassian. Identify the app and relevant site/account only as needed for verification. Choose the Privacy request category above. This form does not perform an automated erasure action. See the privacy policy.

Read the setup and troubleshooting guide →