...
| Table of Contents | ||
|---|---|---|
|
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:
Setup and Usage Instructions
| Info |
|---|
This process can only be completed by a Jira Admin. |
...
Clicked ‘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.
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.
...
| 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.
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
| Info |
|---|
This process can only be completed by a Jira Admin. |
...
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
| Info |
|---|
This process can only be completed by a Jira Admin. |
...
| 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. |
Related information
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...