Favro's Jira integration allows you to sync cards and issues across both platforms.

To set up the self-hosted Jira Integration:

  1. Open board settings (...) > More > Integrations and API... > Jira

2. Click the "Connect to Jira" button > Select the "Self-hosted Jira" option

3. Add any instance name into the "Configuration name" field

4. Click the "Connect" button

5. Copy the access token of your connection from the Pending connections list

6. Navigate to your own Jira self hosted instance > "Administration" menu > Manage apps > Search for "Favro integration" > Install "Favro Integration" app

7. Manage apps > Favro Integration > Configure

8. Insert an email address in the "Email" field > press ‘’Save email address’’. This email will be used to create a new Jira user to sync and update issues in Jira. The email should be secure and not personal/work email in order to avoid someone gaining access to your Jira instance.

9. Paste access token into "Access token" field > Click "Add connection " button

10. Open board settings (...) > More > Integrations and API... > Jira to configure/customize filters

10. Navigate to your own Jira self hosted instance > Issues > Select a filter you want to connect

11. Copy Filter ID from URL field

12. Navigate back to Favro > Paste the copied filter ID into the "Filter ID" field

13. Click the "Connect" button

Now you have the self-hosted Jira Integration enabled. In order to have the 2 - way sync you will need to map statuses, see instructions To set up mapping Jira issue workflow statuses to Favro board columns further bellow.


To set up the Jira Cloud hosted by Atlassian Integration

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Click the "Connect to Jira" button > Select "Jira Cloud hosted by Atlassian" option

3. Add any instance name into the "Configuration name" field and add your Jira Cloud link into the "Jira address" field (e.g. https://example.atlassian.net)

4. Navigate to your Jira instance > Apps > Find new apps > Search for "Favro integration" > Install "Favro Integration" app

5. Navigate to Apps > Manage your apps > Favro Integration > Configure

6. Copy access token

7. Paste access token into "Jira cloud add-on access token" field in Favro

8. Click the "Connect " button

9. Open board settings (...) > More > Integrations and API... > Jira

10. Select a connection from "Established connections" list > Click on the "Connect filter" button

11. Navigate to your Jira instance > Filters > View all filters > Select a project you want to connect

12. Copy the Filter ID from the URL field

13. Navigate back to Favro > Paste the copied filter id into the "Filter ID" field

14. Click the "Connect" button

Note:

  • Favro will sync only issues applied to the selected Jira filter. If the issue is moved out of the selected filter in Jira, it will be archived on the Favro board and all changes made to it won't be synced to Favro

    • If the issue was moved back to filter it will be unarchived in Favro

  • To sync multiple Jira boards to your Favro board you need to connect multiple Jira filters. Issues from all connected Jira boards will be sent to the Favro board and will be synced.


To set up mapping Jira issue workflow statuses to Favro board columns

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Select a connection from the "Established connections" list > Click the "Create mapping" button

3. In the opened window set parameters for the following fields:

  • Favro column (column in Favro to which mapping will be applied)

  • Issue type

  • Transition ID (ID of Jira column to which mapping will be applied)

  • Resolution (resolution the issue will receive in Jira)

4. Click the "Create" button

Users can add multiple mapping configurations, edit and remove them.

Note: The resolution dropdown contains all resolution statuses in the current Jira project. Resolutions set in Favro mapping settings won't be applied to Jira issue resolution. Instead, the resolution will be changed according to resolution configurations set for each column in Jira.

After applying mapping configurations to the Favro board, users will be able to change card status on Favro and it will be automatically changed in Jira.


Note: To have mapping from Jira status to Favro status, you would need to set up automation inside Favro to have the status updated.

Jira status field will update automatically when you move cards in Jira. Automation would need to be set by this field as it changes and can be mapped. Here is an example of how you can set it up:

Mapping only applies for issue types mentioned in mapping settings (e.g. story type issue won't change its status in Jira if task issue type is set in mapping settings)


To find the column Transition ID

  1. Navigate to your Jira instance > "Settings" menu > Issues

2. In the left menu select "Workflows" > Click the "View" button next to the project you need

3. Switch to the “Text” view > Copy Transition ID (numeric value in the brackets next to Jira column name)


To connect User Sync

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Connect Jira Integration and Jira filter

  3. Toggle on "Sync users between Favro and Jira" > Press the "Turn on" button


To Setup automatic card-sending from Favro to Jira

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Click the "Setup Favro to Jira" button

3. Fill the following fields:

  • Jira connection address

  • Project

  • Issue type

  • Parent issue key (sub-task issue type only) - parent Jira issue id for your sub-task

4. Click the "Confirm" button

After enabling automation settings, all cards created on the Favro board will be sent to Jira automatically with the mentioned parameters.

ATTENTION: Favro's Jira integration supports the following three card fields 'summary", "description" and "assignee" this ensures a more straightforward and streamlined integration process without the hassle of complex setups that break the integration whenever the configuration changes in Jira.

Users are able to edit automation settings by clicking on the “Edit Favro to Jira” button:

And can remove the automation by clicking on the “Remove” button from “Automation” modal:


To disconnect the Jira Integration

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Click the "Disconnect from x boards" button next to any instance in the "Established connections" list

3. Confirm disconnection by clicking “Disconnect from all boards” in the popup window

Disconnection applies to the entire organization. The integration disconnects each board in each collection. After disconnecting the Jira Integration, any changes made to a card are not synced until the integration is reconnected. After reconnection, all changes made in Jira without a connection will be synced to Favro.


To disconnect the Jira filter

  1. Open board settings (...) > More > Integrations and API... > Jira

  2. Click the "Remove filter" button next to the filter connected to the Jira instance

3. Confirm filter disconnection by clicking on the “Remove” button in the confirmation window

After disconnecting the Jira filter all issues synced from the disconnected filter will be removed from the Favro board.


Permission to Jira integration

There are two options on how you can set permissions for Jira integration:

a) Allow only administrators to manage the connection to Jira in the whole organization, you can find more on that in this article: Jira integration control for Enterprise organizations.

b) Administrator Allow/Disallow members to configure Jira integration on specific boards.

To edit permissions:

  1. Open board settings (...) > Permissions

  2. Toggle on/off "Members can configure this board"

If "Members can configure this board" is toggled on, all Members have permissions to connect, disconnect and configure Jira Integration. Otherwise, only administrators have permission to configure the Jira Integration on that board.

If the Jira Integration is connected to more than one board only Admin users have permission to disconnect the Jira Integration.

Did this answer your question?