Note | ||||||
---|---|---|---|---|---|---|
This Marketplace The
If you encounter any issues while using the App, please contact support@teamform.coraise a support request using the |
The TeamForm
Atlassian for Jira
Marketplace App is for existing TeamForm
customers who also use using Atlassian’s Jira Cloud SaaS product.
Tip |
---|
The |
Tip |
---|
You can link a whole Project to a Team in TeamFrom. |
Tip |
---|
TeamForm can use the TeamForm Marketplace App to import Jira Issues as TeamForm Objectives. |
Setup & Usage Instructions
Info |
---|
This process can only be completed by a their respective team pages in TeamForm. This creates transparency on which team is working on which work. |
Table of Contents | ||
---|---|---|
|
Why use the TeamForm for Jira App
With our TeamForm for Jira
App, your organisation’s Jira Administrators can link
Jira Projects to relevant TeamForm Teams. This allows a Jira user to click through from Jira to TeamForm to view the team and team members who deliver this project.
We also offer a TeamForm integration, that combines with the TeamForm Jira app, to import Issues from Jira into TeamForm - displaying this team’s work items as Objectives.
Prerequisites
Identify your Jira Admin, you will need their help to establish the initial App Configuration.
Note |
---|
TeamForm Public API: If you have not setup |
Note |
---|
IP Based Restrictions: If your A current list of Atlassian IPs can be found under the |
Initial Setup
Note |
---|
This step 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-jiraWithin Jira, navigate to the
Admin Page
for the Marketplace App:
...
On the
Admin Page
, fill in yourTeamForm Public API
details including:Tenant ID
Client ID and Client Secret provided to you by TeamForm (located via the help?
icon on the bottom left menu of TeamForm)Workspace ID
(if left blank, the plugin will use TeamForm’s default Workspace)
...
If you have not requested Public API access, you can request them for your Tenant by emailing support@teamform.co.
...
Client ID
andClient Secret
(refer below for TeamForm API steps)Optional: If you use a
Custom TeamForm URL
to connect to TeamForm, you can enter it on this page.
...
...
e.g.
company.teamform.co
Click
Change
with each of the new setup details.
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.
...
Tip |
---|
Congratulations! You can now start to |
Info | ||||||||
---|---|---|---|---|---|---|---|---|
Note
|
How-to Use
Project Linking
To link a project to one (or many) TeamForm Team(s):
Click on
TeamForm
on the left-hand sidebarNote: on smaller screens, you might need to scroll down
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’
link
it to this Issue: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
e.g. typing: ‘customer', which should return 'Customer Success’ as the top result.
...
Note |
---|
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.
Once a team is linked, Jira issues will be synchronised to TeamForm however frequently the integration is configured for - every 15 minutes by default.
Tip |
---|
🎉 Congratulations - you have created a The Team will appear in a side panel for any issue owned by this Team. You can now jump straight to the Team in TeamForm, by clicking its name. |
Issue Linking
Status | ||||
---|---|---|---|---|
|
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.
...
Try typing: ‘customer', which should return 'Customer Success’ as the top result.
...
Note |
---|
If you need to remove a Team's Issue link, click the 'x' to the right of the Team in the list. |
Tip |
---|
🎉 Congratulations, you have made a The Team will appear in a side panel for any issue owned by this Team. You can now jump straight to the Team in TeamForm, by clicking its name. |
Mapping Issue Types to Team Types
Info |
---|
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 theTeamForm for 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’
Change
Enter your Team Type ID in the text field.
Click ‘Create’.
Create
You can add multiple mappings to the same Jira Issue Type.
You can remove a mapping by clicking on it.
Click ‘Done’.
...
Done
Linking & Importing
There are two types of linking.
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 in TeamForm on a Teams page
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)
Setting up Jira Issue Types to Show in TeamForm
Info |
---|
This process can only be completed by a Jira Admin. We recommend only importing a subset of Issue types into TeamForm, so that only meaningful work items are visible in TeamForm, rather than work items of varying size and granularity This section details how to |
On the
Admin Page
of theTeamForm for Jira
Marketplace App, click theReveal
button to show a secret URL and Key (note: These are the credentials to be put into the Integration form)Select which Issue Types you would like to include in the Import, by using the
Included
column.Click
Excluded
on the Issue Type you wish to import, to toggle it toIncluded
.
...
Note |
---|
Remember: even though an Issue Type is selected, only some of the Issues with that Issue Type will be imported: e.g only those whose Project is |
Setting up Jira Integration from TeamForm
Log into your TeamForm instance, and navigate to the ‘Data Integrations’
Data Integrations
Settings Page.Click
Create
on ‘New Integration’.New Integration
Select ‘Atlassian Jira'.
Connect
next toAtlassian Jira
Click
Create datasource
.Paste the
Key
andURL
revealed earlier into the relevant fields.Click ‘Update’.
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 pluginconnect with the TeamForm for Jira
App, and import any Issue of a Type that has been mapped to a Team Type in TeamForm.
Note |
---|
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. |
Note |
---|
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.not recommended to map Jira Tasks, Bugs, Stories as they are not a helpful granularity of work to display in TeamForm. |
Tip |
---|
Excellent! You have now configured TeamForm to import Projects and Issues from Jira, using the Atlassian TeamForm Integration. |
Other TeamForm for Jira Config settings
Admin Page (Customised Message)
This section of the Admin Page is used to customise the appearance of the App for projects not yet linked to teams.
Set Un-linked default text
is used to customise the message shown when an Issue or Project is not linked to a Team - to this set up:
Enter your custom message into the text box. You could use the following, as an example:
Code Block Please go to this <a href='https://www.example.co' target='_blank'>link</a> if you need TeamForm access
...
Click
Save default text
...
Admin Page (Permissions)
You can restrict who is able to link TeamForm Teams to projects in Jira:
...
Related information
Filter by label (Content by label) | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|