You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contents/docs/error-tracking/assigning-issues.mdx
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,7 @@ title: Assign issues to teammates
4
4
5
5
Error tracking enables you to assign issues to specific PostHog [roles](https://app.posthog.com/settings/organization-roles) or teammates. This helps your team find relevant issues through **filtering**. You can also set up team-specific **alerting** to notify them when assigned issues are created or reopened.
6
6
7
-
8
-
## Assigning issues
7
+
## Assign issues
9
8
10
9
You can manually assign issues as you triage them in the UI. This can be done both in the issue list and issue detail pages.
11
10
@@ -50,15 +49,15 @@ Here are some common properties you can filter on:
50
49
51
50
| Property | Event property | Description |
52
51
| --- | --- | --- |
53
-
| Exception type |`$exception_types`| The type of exception(s) that occurred.|
54
-
| Exception message |`$exception_values`| The message(s) detected on the error.|
55
-
| Exception function |`$exception_functions`| The function(s) where the exception occurred.|
56
-
| Exception source |`$exception_sources`| The source file(s) where the exception occurred.|
57
-
| Exception was handled |`$exception_handled`| Whether the exception was handled by the application.|
58
-
| Device type |`$device_type`| The type of device that the error occurred on.|
59
-
| Browser |`$browser`| The browser that the error occurred in.|
60
-
| Current URL |`$current_url`| The URL that the error occurred on.|
61
-
| Feature flag |`$feature_flag`| The feature flag that the error occurred on.|
52
+
| Exception type |`$exception_types`| The type of exception(s) that occurred |
53
+
| Exception message |`$exception_values`| The message(s) detected on the error |
54
+
| Exception function |`$exception_functions`| The function(s) where the exception occurred |
55
+
| Exception source |`$exception_sources`| The source file(s) where the exception occurred |
56
+
| Exception was handled |`$exception_handled`| Whether the exception was handled by the application |
57
+
| Device type |`$device_type`| The type of device that the error occurred on |
58
+
| Browser |`$browser`| The browser that the error occurred in |
59
+
| Current URL |`$current_url`| The URL that the error occurred on |
60
+
| Feature flag |`$feature_flag`| The feature flag that the error occurred on |
62
61
63
62
You can also set custom properties on the error tracking event to filter on. For example, setting a custom `params_received` property to provide more context or debug information.
64
63
@@ -68,4 +67,21 @@ Issue assignment filters are evaluated in the order they are configured. They ca
68
67
69
68
### Alerting based on assignment
70
69
71
-
A common use case for automatic issue assignment is to alert assignees of new issues. Once the issues are automatically assigned, you can set up alerts to notify the assignee. See the [alerts](/docs/error-tracking/alerts) guide for more information.
70
+
A common use case for automatic issue assignment is to alert assignees of new issues. Once the issues are automatically assigned, you can set up alerts to notify the assignee. See the [alerts](/docs/error-tracking/alerts) guide for more information.
71
+
72
+
## Create external issues
73
+
74
+
You can also create issues in external tracking systems like GitHub Issues, Linear, or GitLab.
75
+
76
+
First, set up an [integration](/docs/error-tracking/integrations) with your tracking system. Then, from an issue's details page, under **External references**, click **Create issue**.
alt="Error tracking create issue in external tracking system"
82
+
classes="rounded"
83
+
/>
84
+
85
+
The new issue will have a partial stack trace and a link to the issue in PostHog.
86
+
87
+
> If you use another issue tracking system and would like to request it, [let us know in-app](https://app.posthog.com#panel=support%3Afeedback%3Aerror_tracking%3Alow%3Atrue).
PostHog integrates with GitHub, GitLab, and Linear to enhance error tracking with source code context, commit information, and external issue tracking.
6
+
7
+
| Integration | Capabilities |
8
+
|-------------|-----------------|
9
+
|[GitHub](#github-integration)| Pinpoint Git commits that cause issues, open files in GitHub directly from stack traces, and create GitHub issues from errors |
10
+
|[GitLab](#gitlab-integration)| Pinpoint Git commits that cause issues, open files in GitLab directly from stack traces, and create GitLab issues from errors |
11
+
|[Linear](#linear-integration)| Create Linear issues directly from errors and track fixes in your existing Linear workflows |
12
+
13
+
## GitHub integration
14
+
15
+
To set up the GitHub integration:
16
+
17
+
1. Go to [Error tracking settings](https://app.posthog.com/settings/project-error-tracking) in the PostHog app and find **Integrations**
18
+
2. Under **GitHub**, click **Connect organization**
19
+
3. Authorize PostHog to access your repositories
20
+
4. Select the repositories you want to link
21
+
22
+
PostHog connects to GitHub by installing a GitHub application. PostHog needs the following permissions:
23
+
24
+
- Read access to metadata
25
+
- Read and write access to code, issues, and pull requests
26
+
27
+
Once connected, create a [release](/docs/error-tracking/releases) to start using source linking.
28
+
29
+
## GitLab integration
30
+
31
+
To set up the GitLab integration:
32
+
33
+
1. Go to [Error tracking settings](https://app.posthog.com/settings/project-error-tracking) in the PostHog app and find **Integrations**
34
+
2. Under **GitLab**, click **Connect project**
35
+
3. Provide the following information:
36
+
- Hostname
37
+
- Project ID
38
+
- A project access token with the `api` scope
39
+
40
+
PostHog connects to GitLab using a [project access token](https://docs.gitlab.com/user/project/settings/project_access_tokens).
41
+
42
+
Once connected, create a [release](/docs/error-tracking/releases) to start using source linking.
43
+
44
+
## Linear integration
45
+
46
+
Connect your Linear workspace to create and track Linear issues directly from error tracking.
47
+
48
+
To set up the Linear integration:
49
+
50
+
1. Go to [Error tracking settings](https://app.posthog.com/settings/project-error-tracking) in the PostHog app and find **Integrations**
51
+
2. Under **Linear**, click **Connect workspace**
52
+
3. Authorize PostHog to access your Linear workspace
53
+
54
+
PostHog connects to Linear using a [third-party app](https://linear.app/docs/third-party-application-approvals). PostHog needs the following permissions:
55
+
56
+
- Create issues for your workspace
57
+
- Read access to your workspace
58
+
59
+
## What's next?
60
+
61
+
After setting up an integration:
62
+
63
+
1.[Upload source maps](/docs/error-tracking/upload-source-maps) for better stack traces
64
+
2.[Create releases](/docs/error-tracking/releases) to link errors to specific deployments
65
+
3.[Create external issues](/docs/error-tracking/assigning-issues#creating-external-issues) from PostHog
Copy file name to clipboardExpand all lines: contents/docs/error-tracking/releases.mdx
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,4 +27,16 @@ When you [upload sourcemaps](/docs/error-tracking/upload-source-maps/) using `po
27
27
28
28
## Release context in error tracking
29
29
30
-
Other than a specific release version that you define, captured exceptions inherit the release information recorded during injection. PostHog attaches the release, project, and Git metadata to each exception captured as we capture it in our ingestion pipeline.
30
+
Other than a specific release version that you define, captured exceptions inherit the release information recorded during injection. PostHog attaches the release, project, and Git metadata to each exception captured as we capture it in our ingestion pipeline.
31
+
32
+
## Source linking
33
+
34
+
Releases enable source linking in stack traces. When you create a release with repository information, PostHog can link each stack frame to the exact file and line in your GitHub or GitLab repository.
35
+
36
+
To use source linking:
37
+
38
+
1. Set up a [GitHub or GitLab integration](/docs/error-tracking/integrations)
39
+
2. Create a release that includes your repository and commit information
40
+
3. PostHog automatically adds **View commit** buttons to stack traces
41
+
42
+
This makes it faster to investigate errors by jumping directly from the stack trace to your source code. Learn more about [stack traces](/docs/error-tracking/stack-traces#source-linking).
Copy file name to clipboardExpand all lines: contents/docs/error-tracking/stack-traces.mdx
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,19 @@ Error tracking displays release information over stack traces to help you track
42
42
43
43
Learn more about [releases](/docs/error-tracking/releases/) in error tracking.
44
44
45
+
## Source linking
46
+
47
+
When viewing stack traces in PostHog, you can click directly through to the relevant code in your GitHub or GitLab repository. Each stack frame includes a **View commit** button (displayed using a GitHub or GitLab icon) that links to the exact file and line where the error occurred.
Source linking requires a [GitHub or GitLab integration](/docs/error-tracking/integrations) and a [release](/docs/error-tracking/releases) with repository information. Once set up, PostHog automatically adds source links to your stack traces.
57
+
45
58
## Troubleshooting symbol sets
46
59
47
60
Compiled or minified languages requires additional information to perform a process called symbolification to produce the same stack trace and code context output shown above. The additional information is known as a symbol set.
0 commit comments