Content Comparison

...

...

...

...

Setup & Usage Instructions

1. Install the 'TeamForm for Jira' Marketplace App into your Jira Cloud instance.

   1. A link to the Marketplace App is here: https://marketplace.atlassian.com/apps/1232958/teamform-for-jira

2. Within Jira, navigate to the Admin Page for the Marketplace App:

...

Image Removed

3. On the Admin Page, fill in your TeamForm Public API details including Tenant ID, Client ID and Client Secret provided to you by TeamForm

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.

Image Added

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.

Image Added

Installing the TeamForm for Jira App

Prerequisites

Identify your Jira Admin, you will need their help to establish the initial App Configuration.

TeamForm for Jira App Setup request:
- please provide: Client Credentials (ID and Secret)

Access Level: <production, staging, test etc>
Tenant ID: <tenant id (as found above)>
Workspace ID: <workspace id>
Security Contact: <your email, or the email of the person responsible for the secure storage of the Client Credentials>
Atlassian Jira URL: <xyz.atlassian.net>

...

Installation and Setup

1. 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

2. Within Jira, navigate to the Admin Page for the Marketplace App:

Image Added

3. On the Admin Page, fill in your TeamForm Public API details including:

   1. Tenant ID (located via the help ? icon on the bottom left menu of TeamForm)

   2. Workspace ID (if left blank, the plug-in will use TeamForm’s default Workspace)

   3. Client ID and Client Secret (refer below for TeamForm API steps)

   4. Optional: If you use a Custom TeamForm URL to connect to TeamForm, you can enter it on this page.
      e.g. company.teamform.co

   5. Click Change with each of the new setup details.

How-to Use

Project Linking

To link a project to one (or many) TeamForm Team(s):

1. Click on TeamForm on the left-hand sidebar

   • Note: on smaller screens, you might need to scroll down

   • This will show the Project-level settings for the App.

2. To assign a Team, click the select box at the bottom of the panel.

3. Click on one of the Teams to link it to this Jira Project.

4. To search for other Teams in TeamForm, type the name, or part of a name into the select box. The App will query TeamForm, and show potential Teams relevant to your search term.

   • e.g. typing: ‘customer', which should return 'Customer Success’ as the top result.

5. Once a team is linked, Jira issues will be synchronised to TeamForm however frequently the integration is configured for - every 15 minutes by default.

Issue Linking

Status
colour Blue title beta

1. Head to an Issue on any Jira board on the current Instance:

2. Click on ‘TeamForm Team’ on the right-hand side.

Image Added

3. A panel will open, showing that this issue is currently ‘Unassigned’ to a TeamForm Team.

...

4. To assign a Team, click the select box at the bottom of the panel.

   • Click on one of the Teams to

...

3. • link it to this Issue:

...

Image Added

4. 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.

...

4. Try typing: ‘customer', which should return 'Customer Success’ as the top result.

...

Project Linking

To link a project to one (or many) TeamForm Team(s):

...

Click on ‘TeamForm’ on the left-hand sidebar.

1. 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.

...

Image Added

6. To remove the link between a team and an issue, click the

   Status
   colour Blue title X

   button to the right of the listed teams.

Mapping Issue Types to Team Types

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 TeamForm for Jira App, and TeamForm can be configured to import all Epics as Objectives to their TeamForm Department on a schedule.

1. Go to the Admin Page of the TeamForm for Jira Marketplace App.

2. Scroll to the bottom of the Admin Page, to the section entitled: Team Type Mappings

3. Make a note of, or copy-paste, a Team Type ID from TeamForm.

   1. You can see a particular Team Type’s ID in the Org Structure section of TeamForm.

4. Find the Issue Type you would like to map to this Team Type.

5. Click Change

6. Enter your Team Type ID in the text field.

7. Click Create

   1. You can add multiple mappings to the same Jira Issue Type.

   2. You can remove a mapping by clicking on it.

8. Click Done

Linking & Importing

There are two types of linking:

1. 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.

   1. They will appear in TeamForm on a Teams page

   2. They are only imported if their Issue Type has been Included (see below)

2. Direct linking: When you link an Issue to a Team, only that Issue is imported as an Objective. No Child Issues are imported.

   1. They are only imported if their Issue Type has been Included (see below)

Setting up Jira Issue Types to Show in TeamForm

1. On the Admin Page of the TeamForm for Jira App, click the Reveal button to show a secret URL and Key (note: These are the credentials to be put into the Integration form).

Image Added

2. 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 to Included.

...

Setting up Jira Integration from TeamForm

1. Log into your TeamForm instance, and navigate to Settings > Data Integrations.

2. Click Create on New Integration

3. Select Connect next to Atlassian Jira

Image Added

4. Click Create datasource
   

...

5. Paste the Key and URL revealed earlier into the relevant fields

6. Click Update

7. 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 connect with the TeamForm for Jira App, and import any Issue of a Type that has been mapped to a Team Type in TeamForm.

Other Configuration settings for the TeamForm for Jira App

Customised Message (admin page)

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:

1. Enter your custom message into the text box. You could use the following, as an example:

   • Please go to this <a href='https://www.example.co' target='_blank'>link</a> if you need TeamForm access.

Image Added

2. Click Save default text.

Image Added

Permissions (admin page)

This section of the admin page is to restrict who is able to link TeamForm Teams to projects in Jira:

...

Grouping by Custom Field

Some organisations use a Custom Field to define a higher level strategy or work item that Jira issues contribute to, or are grouped under. These might be called Strategic Goals, Themes or Objectives (or any other term used to define higher level work). You can configure the TeamForm for Jira app to recognise custom fields so that links between these and Jira issues are visible in TeamForm.

1. You can learn how to create a Custom Field here: https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

   1. Only Single Select and Multi Select drop-down Field Types are supported.

2. Once you have set up your Custom Field, go to the Jira Admin page, and head to the Custom Fields section.

3. Click Expand.

4. Select, or type to search, from the drop-down list as many Custom Fields you wish to use - most people just use one.

5. Click Submit - you should receive a message saying your changes have been submitted.

Example

Linking the Theme Custom Field to a high level objective shown in TeamForm:

...

Image Added

Image Added

Custom field: TeamFormSelect

Expand

This custom field allows users to embed a teamform connected select within Jira. Info Why would you use this? Maybe you want to associate a team as a dependency. Or perhaps design a workflow that references teams. This field allows you to have a field that displays and allows association of TeamForm teams with the customisation of naming, which team types are shown and whether to allow association with just one or multiple teams.   Configuration Options Select team types to filter by - This select is connected to the 'GroupTypes' configuration object and allows an admin to configure what teams the Custom Field can query/search against. It is a multi-select, allowing the admin to show multiple team types in the results. Image Added   Allow user to select multiple teams - This checkbox determines whether the CustomField allows multiple values, or only a single value. Image Added   JQL and TeamformSelect There are two ways of querying a CustomField. Option 1: "My Custom Field" {{operator}} {{value}} IS - This operator is only usable with EMPTY or NULL checking for an empty value and will not trigger the autosuggest. See more at Jira documentation. IS NOT - This operator is only usable with EMPTY or NULL checking for an empty value and will not trigger the autosuggest. See more at Jira documentation. CONTAINS (~) - The "~" operator is used to search for issues where the value of the specified field matches the specified value (either an exact match or a "fuzzy" match — see examples in Jira documentation). See more at Jira documentation.   CONTAINS (~) - The "!~" operator is used to search for issues where the value of the specified field is not a "fuzzy" match for the specified value. See more at Jira documentation.   Option 2: "My Custom Field.Name" {{operator}} {{value}}   IS - This operator is only usable with EMPTY or NULL checking for an empty value and will not trigger the autosuggest. See more at Jira documentation. IS NOT - This operator is only usable with EMPTY or NULL checking for an empty value and will not trigger the autosuggest. See more at Jira documentation.   IN - This operator searches for issues where the value of the specified field is one of multiple specified values. The values are specified as a comma-delimited list, surrounded by parentheses. See more at Jira documentation. NOT IN - This operator searches for issues where the value of the specified field is not one of multiple specified values. The values are specified as a comma-delimited list, surrounded by parentheses. See more at Jira documentation. = - This operator searches for issues where the value of the specified field matches exactly the specified value. See more at Jira documentation. != - This operator searches for issues where the value of the specified field does not match the specified value. See more at Jira documentation.

Related information