Ticketify LogoAn animated "T" logo with a gradient border and glowing effect Ticketify
Back to Blog

Tips & Tricks

Fine-Tuning Your AI Tickets: Mastering the Advanced Sliders

Ticketify Tips Team's profile picture - author of this article
Ticketify Tips Team
April 25, 2025 4 min read 678 words
AITicket GenerationCustomizationBest PracticesWorkflow

Introduction: Beyond the Basics

You've generated your first few tickets with Ticketify, and it's already saving you time. But did you know you can achieve even greater precision and control over the output? The key lies in mastering the four advanced sliders: Formality, Technical Detail, Text Volume, and Urgency.

These sliders allow you to fine-tune the AI's approach, ensuring the generated ticket perfectly matches the context, audience, and purpose. Let's break down what each slider does and when to adjust it.

1. Formality

Controls: The overall tone and language style of the ticket.

  • Low (0-30): Casual, direct language. Might use contractions or simpler sentence structures. Suitable for internal team communication where everyone shares context.
  • Medium (31-70): Standard professional tone. Balanced, clear, and generally appropriate for most situations. This is the default setting.
  • High (71-100): Formal, structured language. Avoids colloquialisms, uses more complex sentences. Ideal for tickets shared with external stakeholders, formal bug reporting systems, or compliance documentation.

Example Use Cases:

  • Low: A quick task reminder for a teammate.
  • High: A bug report submitted to a vendor or for an official audit trail.

2. Technical Detail

Controls: The level of technical jargon, implementation specifics, and depth included.

  • Low (0-30): Focuses on the user experience and functional impact. Avoids code snippets or deep system details. Best for user stories, high-level tasks, or tickets intended for non-technical audiences (e.g., product managers, designers).
  • Medium (31-70): Includes standard technical details like component names, steps to reproduce, and expected technical outcomes. Suitable for most development tasks and bug reports within the engineering team.
  • High (71-100): Dives deep into technical specifics. May suggest potential code locations, mention specific APIs or database tables, or include detailed error logs. Use when reporting complex bugs, defining intricate technical tasks, or communicating with specialized engineers (e.g., backend, security).

Example Use Cases:

  • Low: A user story describing a new feature from the user's perspective.
  • High: A bug report detailing a specific API endpoint failure with request/response logs.

3. Text Volume

Controls: The overall length and verbosity of the generated ticket.

  • Low (0-30): Concise and to the point. Provides only the essential information. Good for simple tasks or when brevity is valued (e.g., quick backlog items).
  • Medium (31-70): Balanced length. Provides sufficient detail without being overly wordy. The default setting, suitable for most standard tickets.
  • High (71-100): Very detailed and comprehensive. Expands on context, provides extensive background, and elaborates on each section. Useful for complex epics, detailed bug reports requiring lots of context, or tickets serving as documentation.

Example Use Cases:

  • Low: A task to update a dependency version.
  • High: An epic outlining a major new feature set with background, goals, and detailed requirements.

4. Urgency

Controls: The tone and language used to convey the importance and time sensitivity of the ticket. Note: This primarily affects the language, not necessarily the final Priority/Severity fields, although it can influence them.

  • Low (0-30): Neutral, standard language regarding priority. Suitable for routine tasks or low-priority bugs.
  • Medium (31-70): Slightly emphasizes importance. May use phrases indicating moderate priority. Appropriate for standard priority tasks or bugs.
  • High (71-100): Uses strong language to convey high importance and time sensitivity (e.g., "critical," "blocker," "immediate attention required"). Best for critical bugs, production issues, or high-priority tasks with tight deadlines.

Example Use Cases:

  • Low: A feature request for a future release.
  • High: A production outage bug report.

Finding Your Balance

The ideal settings often involve combining slider adjustments:

  • Formal Bug Report: High Formality, High Technical Detail, Medium/High Volume, High Urgency.
  • Simple Dev Task: Low/Medium Formality, Medium Technical Detail, Low/Medium Volume, Low Urgency.
  • User Story for PM: Low Formality, Low Technical Detail, Medium Volume, Medium Urgency.

Experiment with the sliders based on your input text and desired output. Mastering these controls elevates Ticketify from a simple generator to a precise communication tool, ensuring your tickets are always perfectly tailored to the situation.