Custom Dimensions
- David Simpson
Each custom dimension allows you to filter data within Google Analytics based on a separate criteria, such as project key or project name, or show all issues where the status (name or ID) is a particular value.
Index | Custom Dimension | Scope | Description |
|---|---|---|---|
1 | Project Key | Hit | An alphabetical string |
2 | Project ID | Hit | A number |
3 | Atlassian Account ID | User | The user identifier for an individual user |
4 | Project Name | Hit | The name of the project |
5 | Issue Key | Hit | e.g. ABC-123 |
6 | Issue ID | Hit | A number |
7 | Issue Type ID | Hit | A number |
8 | Issue Summary | Hit | Also sent as the page title for issue pageviews |
9 | Issue Status ID | Hit | A number |
10 | Issue Status Name | Hit | A string |
11 | Issue View Context | Hit | Describes the context in which the issue is displayed. See below for further details |
12 | Group Names | User | A comma separated list of the names of all the groups a user is a member of. Allows for filtering of reports based on groups and is human readable. |
Issue View Context
Jira issues can be viewed in several different places within the Jira interface.
The Issue View Context custom dimension allows you to easily differentiate whether the pageview was within the Jira Service Management portal (where Issue View Content equals jsd.portal.view), or within the standard Jira interface (where Issue View Content starts with jira).
A full list of Issue View Context values is tabulated below:
Issue View Context | Description |
|---|---|
| Jira Service Management portal view (the customers' view) |
| Jira Service Management Agents view |
| The standard Jira Issue View |
| An issue viewed in a list of Jira issues |
| An issue viewed in a planning board |
| An issue viewed in a standard Jira agile board |
| All other views |
More Issue View Contexts will be added, when the Jira user interface changes, as required.
.