The TeamForm for Jira App
is currently in BETA
If you encounter any issues while using the App, please raise a support request using the contact us
option at the bottom of the page.
The TeamForm Atlassian Marketplace App is for existing TeamForm customers using Atlassian’s Jira Cloud SaaS product.
The Marketplace App allows customers to ‘link’ their Jira Issues with Teams in TeamForm.
You can link a whole Project to a Team in TeamFrom.
TeamForm can use the TeamForm Marketplace App to import Jira Issues as TeamForm Objectives.
Why?
Once the plugin is installed and configured, you can link
Projects, as well as Issues (e.g Epics, Initiatives or Stories) to TeamForm Teams. Once linked
, you may easily switch between TeamForm and Jira by clicking on the hyperlinks created and manged in both Jira and TeamForm:
Initial Setup
Prerequisites:
Prerequisites
TeamForm Public API: If you have not setup TeamForm Public API
access, you can request them for your TeamForm Tenant
by raising a support request, using the contact us
option at the bottom of the page. More information via TeamForm Public API
Note: If your TeamForm tenant
is configured with IP based restrictions
you will also need to request the Atlassian IPs
be added (also via the contact us
option)
A current list of Atlassian IPs can be found under the Outgoing Connections
section on this page https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/
This process can only be completed by your Jira Admin
Install the 'TeamForm for Jira' Marketplace App into your Jira Cloud instance.
A link to the Marketplace App is here: https://marketplace.atlassian.com/apps/1232958/teamform-for-jira
Within Jira, navigate to the Admin Page for the Marketplace App:
On the Admin Page, fill in your TeamForm Public API details including:
Tenant ID
Client ID and Client Secret provided to you by TeamForm
Workspace ID (if left blank, the plugin will use TeamForm’s default Workspace)
Optional: If you use a Custom URL to connect to TeamForm, you can enter it on this page.
e.g.company.teamform.co
Clicked
Change
with each of the new setup details.
How-to Use
Issue Linking
Head to an Issue on any Jira board on the current Instance:
Click on ‘TeamForm Team’ on the right-hand side.
A panel will open, showing that this issue is currently ‘Unassigned’ to a TeamForm Team.
To assign a Team, click the select box at the bottom of the panel. Click on one of the Teams to ‘link’ it to this Issue:
To search for other Teams in TeamForm, type the name, or part of a name into the select box. The Marketplace App will query TeamForm, and show potential Teams relevant to your search term.
For example, try typing: ‘customer', which should return 'Customer Success’ as the top result.
If you need to remove a Team's Issue link, click the 'x' to the right of the Team in the list.
Project Linking
To link a project to one (or many) TeamForm Team(s):
Click on ‘TeamForm’ on the left-hand sidebar.
This will show the Project-level settings for the App.
To assign a Team, click the select box at the bottom of the panel.
Click on one of the Teams to ‘link’ it to this Jira Project.
To search for other Teams in TeamForm, type the name, or part of a name into the select box. The Marketplace App will query TeamForm, and show potential Teams relevant to your search term.
For example, try typing: ‘customer', which should return 'Customer Success’ as the top result.
Once a team is linked, your Jira issues will be synchronised to TeamForm however frequently the integration is configured for - every 15 minutes by default.
Mapping Issue Types to Team Types
This process can only be completed by a Jira Admin.
For example, in your company, Epics might be completed by your organization's Departments. By mapping Jira Epics to TeamForm Departments, only Departments will be selectable in the Jira Marketplace App, and TeamForm can be configured to import all Epics as Objectives to their TeamForm Department on a schedule.
Go to the Admin Page of the Jira Marketplace App.
Scroll to the bottom of the Admin Page, to the section entitled: Team Type Mappings
Make a note of, or copy-paste, a Team Type ID from TeamForm.
You can see a particular Team Type’s ID in the Org Structure section of TeamForm.
Find the Issue Type you would like to map to this Team Type.
Click ‘Change’
Enter your Team Type ID in the text field.
Click ‘Create’.
You can add multiple mappings to the same Jira Issue Type.
You can remove a mapping by clicking on it.
Click ‘Done’.
Linking & Importing
There are two 'levels' of linking supported by the plugin.
Project linking: When you link a Project to a Team, and say that all linked Projects should be imported, any child Issues under those linked projects are also imported.
They will appear as Objectives of the linked TeamForm Team.
They are only imported if their Issue Type has been Included (see below)
Direct linking: When you link an Issue to a Team, only that Issue is imported as an Objective. No Child Issues are imported.
They are only imported if their Issue Type has been Included (see below)
Importing Jira Issues as TeamForm Objectives
This process can only be completed by a Jira Admin.
On the Admin Page of the Jira Marketplace App, click the
Reveal
button to show a secret URL and Key.Select which Issue Types you would like to include in the Import, by using the
Included
column. ClickExcluded
on the Issue Type you wish to import, to toggle it toIncluded
.
Log into your TeamForm instance, and navigate to the ‘Data Integrations’ Settings Page.
Click
Create
on ‘New Integration’.Select ‘Atlassian Jira'.
Click
Create datasource
.Paste the Key and URL revealed earlier into the relevant fields.
Click ‘Update’.
Optional: Configure a schedule for the Integration. This determines how often the data in Jira is automatically imported into TeamForm. For example, to import every 2 hours, use the frequency of
7200
seconds.
The Datasource can now reach out to the Jira plugin, and import any Issue of a Type that has been mapped to a Team Type in TeamForm.
Note: the import process will not find any Issues to import, unless those Issue Types have been mapped to a Team Type in TeamForm. See the relevant section of this document for details.
The import process will import all Issues of mapped Types into TeamForm. This includes Issues in the past. Be sure this is what you want before creating a mapping from an Issue Type to a Team Type.
In particular, it is probably unsafe to create a mapping from Jira Tasks if there are a large amount of Tasks already in Jira.
Related information
Filter by label
There are no items with the selected labels at this time.