Info | ||||||
---|---|---|---|---|---|---|
The TeamForm for Jira App is currently in
If you encounter any issues while using the App, please raise a support request using the |
Tip |
---|
The This creates transparency on which team is working on which work. |
...
Identify your Jira Admin, you will need their help to establish the initial App Configuration.
Note | |||||
---|---|---|---|---|---|
TeamForm Public API: If you have not setup
More information via TeamForm Public API. |
Note |
---|
IP Based Restrictions: If your A current list of Atlassian IPs can be found under the |
Installation and Setup
Note |
---|
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-jiraWithin Jira, navigate to the
Admin Page
for the Marketplace App:
...
Issue Linking
Status | ||||
---|---|---|---|---|
|
Info |
---|
This feature is still in Beta and is still being tested. It may not always behave as expected until final release. |
Head to an Issue on any Jira board on the current Instance:
Click on ‘TeamForm Team’ on the right-hand side.
...
Mapping Issue Types to Team Types
Note |
---|
This process can only be completed by your Jira Admin. |
For example, in your company Epics might be completed by your organization's Departments.
...
Setting up Jira Issue Types to Show in TeamForm
Note |
---|
This process can only be completed by your Jira Admin. |
Info |
---|
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 |
...
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
.
...
Info |
---|
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 |
...
Custom field: TeamFormSelect
Expand | ||||
---|---|---|---|---|
Include Page | | TFW:Advanced Custom Field: TeamFormSelect | TFW:Advanced Custom Field: TeamFormSelect
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.
Allow user to select multiple teams
- This checkbox determines whether the CustomField allows multiple values, or only a single value.
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
Filter by label (Content by label) | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...