> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing.md).

# Issue-level Ticketing

Learn about creating tickets from issues with manual and automated approaches.

Creating tickets from issues represents the primary integration point between Pharos observability and your development workflow. Unlike log-level ticketing, which operates on individual error occurrences, issue-level ticketing works with the aggregated intelligence that Pharos builds around recurring problems.

## Why Issue-level Ticketing

Issues are fingerprinted collections of related logs that share a common root cause. When you create a ticket from an issue rather than an individual log, you're working with enriched context that includes occurrence patterns, user impact metrics, trend analysis, and environmental data accumulated across multiple failures.

This aggregated view makes issue-level ticketing significantly more valuable than creating tickets from isolated log records. Your development team receives a comprehensive picture of the problem rather than a snapshot of a single failure, enabling them to understand the full scope and prioritize appropriately.

{% hint style="success" %}
**The Power of Aggregation**

An issue that occurred 247 times across 18 users over 3 weeks tells a very different story than a single log record. Issue-level ticketing ensures your development team sees that complete narrative, not just a fragment.
{% endhint %}

## The Action and Collaboration Connection

Issue-level ticketing sits at the heart of the [action and collaboration](https://docs.pharos.ai/platform-overview/how-pharos-does-it/action-and-collaboration.md) layer in the Pharos architecture. This layer transforms awareness into resolution by bridging the gap between error detection and development execution.

The workflow follows a natural progression: errors are tracked and aggregated into issues, those issues are triaged and prioritized, and high-priority issues are actioned through ticket creation. This creates a deliberate quality gate where human judgment or well-tuned automation decides which problems warrant development attention versus which can be monitored, documented, or deprioritized.

Without this integration, the gap between detection and resolution becomes a manual bottleneck. Teams spend significant time copying context between systems, lose critical information in translation, and struggle to maintain synchronization as issues evolve. The bugtracker integration automates this flow while preserving—and often enhancing—the context that developers need to resolve issues efficiently.

## Ticketing Approaches

Pharos offers three distinct approaches to creating tickets from issues, each suited to different organizational maturity levels and workflow requirements.

### Manual Creation: The Recommended Starting Point

The [manual ticket creation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/manual-ticket-creation.md) approach uses a create button on the issue detail page, requiring explicit human action to escalate an issue to your development backlog. This is seldom the only approach an organization needs long-term, but it's universally the right place to start.

Why begin manually? Because your organization needs to establish its baseline understanding of what constitutes a ticket-worthy issue before encoding that understanding into automation rules. Those first few weeks of manual triage reveal patterns about which errors actually matter, which are noise, and what criteria distinguish the two. This learning period is invaluable for building effective automation later.

Manual creation also provides selective actioning capability that remains useful even after automation is in place. Some issues require human judgment calls that automation can't replicate—perhaps they're edge cases, perhaps they involve business context not captured in the data, or perhaps they're exceptions to normally automated rules.

### Create-based Automation: Immediate Action

[Create-based triggering](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/create-based-triggering.md) automatically generates tickets when new issues are created, provided they match specified criteria. This represents the most aggressive automation approach—tickets appear in your backlog within seconds of Pharos detecting a new problem pattern.

This approach shines in specific scenarios where immediate action is non-negotiable. Production-critical functional areas like order processing, payment handling, or customer-facing integrations often warrant instant escalation. Organizations with mature error handling and well-tuned fingerprinting can leverage create-based automation to ensure their most important problems get immediate attention.

However, create-based automation requires careful implementation. Without proper criteria refinement, it risks flooding your development backlog with tickets for transient issues, environmental problems, or errors that resolve themselves. This is why understanding your organizational baseline through manual triage is crucial before implementing create-based rules.

### Update-based Automation: The Common Pattern

[Update-based triggering](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/update-based-triggering.md) represents the most common automation strategy in production Pharos deployments. Rather than creating tickets immediately when issues appear, these rules monitor issue evolution and create tickets when problems cross specific thresholds—occurrence counts, user impact levels, or frequency patterns.

This approach offers a natural balance between automation and quality control. Issues that occur once or twice might be transient glitches, but when they reach 50 occurrences across 10 users in a single day, they've proven themselves worthy of development attention. Update-based rules let the data demonstrate the problem's significance before consuming development resources.

The challenge with update-based automation lies in threshold calibration. Set thresholds too low and you generate noise; set them too high and significant issues slip through without tickets. This is another reason why manual triage comes first—it provides the empirical data needed to set meaningful thresholds.

## Reusable Ticketing Actions

[Ticketing actions](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/ticketing-actions.md) provide the building blocks that both manual and automated workflows use to create and update tickets. Rather than configuring ticket creation separately for each use case, you define reusable actions that specify how tickets should be structured, which project they belong to, what priority mapping to use, and what template to apply.

These actions become particularly valuable as you scale your automation. You might have separate actions for production versus sandbox tickets, for different development teams, or for different severities. The same action can be invoked manually via button click or automatically via ticketing rules, ensuring consistency regardless of how the ticket gets created.

Actions also support ticket comments, not just creation. This enables update-based automation to add comments to existing tickets when issues evolve—perhaps when occurrence counts spike, when new users are impacted, or when error patterns change. This keeps your development team informed about issue progression without creating duplicate tickets.

## Choosing Your Approach

Most organizations benefit from a layered strategy that combines multiple approaches:

**Phase 1 (Weeks 1-4):** Begin with purely manual ticket creation. Triage issues daily or weekly, document your decision criteria, and manually create tickets for issues that warrant action. This builds your understanding of what matters in your specific environment.

**Phase 2 (Months 2-3):** Add update-based automation for proven patterns. If you consistently create tickets for issues reaching 25 occurrences with "High" priority in production, encode that as a rule. Continue manual triage for cases that don't match automated patterns.

**Phase 3 (Month 3+):** Consider create-based automation for specific critical functional areas where you have high confidence in fingerprinting and error patterns. Maintain manual and update-based approaches as your safety net for everything else.

{% hint style="warning" %}
**Avoid the Automation Trap**

The ability to automate ticket creation doesn't mean you should automate everything. Organizations that rush to fully automated ticketing before understanding their baseline often end up with development backlogs full of noise, leading to ticket fatigue and eventually disabling the automation entirely.

Start manual, automate gradually, and always measure the signal-to-noise ratio of your automated tickets.
{% endhint %}

## Integration with Triage Process

Issue-level ticketing works hand-in-hand with the [issue triage process](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/triaging.md). Triage establishes priority, validates impact, and determines whether action is warranted. Ticketing executes on that determination by creating the development work item.

The triage-first approach ensures that tickets carry human judgment alongside automated metrics. Even when using automated ticketing rules, those rules should reflect triage criteria—priority levels, functional areas, user impact thresholds, and environmental factors. The ticketing system becomes an extension of your triage methodology rather than a replacement for it.

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>✍️ Manual Ticket Creation</strong></td><td>Using the create button for selective actioning before moving to automation.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/manual-ticket-creation.md">Manual Ticket Creation</a></td></tr><tr><td><strong>🆕 Create-based Triggering</strong></td><td>Automatically creating tickets upon issue creation for viable scenarios.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/create-based-triggering.md">Create-based Triggering</a></td></tr><tr><td><strong>🔄 Update-based Triggering</strong></td><td>Automatically creating tickets on issue updates with fine-tuned criteria to avoid noise.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/update-based-triggering.md">Update-based Triggering</a></td></tr><tr><td><strong>🎬 Ticketing Actions</strong></td><td>Reusable ticketing actions for creation and comments across manual and automated workflows.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/ticketing-actions.md">Ticketing Actions</a></td></tr></tbody></table>

For the execution model and duplicate-ticket safeguards, see [Order of Execution](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/order-of-execution.md).
