How can we help you?

The Jira integration lets you link a support conversation to an issue and follow its progress from FROGED.

Before you start

You need permission to manage integrations and a Jira account with access to the project you will use. Have your Jira domain, account email and API token ready. Treat the token like a password: enter it only in the connection form and never include it in conversations or screenshots.

Connect the account

1. Open Settings > Integrations > All integrations and find Jira.
2. Select the option to install the integration.
3. Enter the short Jira domain: for example.atlassian.net, enter example, without the protocol or .atlassian.net. Complete the email and API token fields.
4. Confirm installation. FROGED checks the details and configures the connection needed to receive Jira events.
5. Review the connected account and the notification preference for closed issues.

If your credentials change, use the account management option and check the connection again. Do not create another integration just to change a token.

Link or create an issue

Open a conversation and find Jira in the information panel. You can link an existing issue or create one by selecting an available project and issue type. Write a summary of the problem without including unnecessary customer data.

Once linked, use the panel to view the issue, open it in Jira or add a comment. Check where each comment will be published: do not confuse a Jira comment with a private note intended to remain only in FROGED.

Follow up and unlink

Jira updates can appear in linked conversations. Closure notifications depend on the configuration and Jira status workflow; check your project using a test issue.

Unlinking removes the relationship with the conversation; it does not delete the Jira issue. Disconnecting the integration is a separate operation that affects the workspace.

Connection problems

If projects do not appear or an action fails, check the domain, token validity and Jira account permissions. Give support the time, error message and conversation/issue references; never send the token.