Content Comparison

...

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:

...

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.

...

Mapping Issue Types to Team Types

For example, in your company Epics might be completed by your organization's Departments.

...

Setting up Jira Issue Types to Show in TeamForm

...

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

...

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.

...

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

   code

   • 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)

You can 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

...