Create Custom Tickets

Start from the Ticket Section

Go to the Tickets section in OneLens, then click the Create Ticket button located at the top right of the page.

You get the custom ticket creation form. Start with defining the scope and objective of your change.

Define the Ticket

Start by setting up the basic ticket details:

• Ticket Title Name the ticket in a way that clearly reflects the change or objective.

• Ticket Status Select the current state of the ticket:

  • To Do: The change hasn’t started yet.

  • In Progress: The change is underway.

  • Acted & Closed: The change has been completed.

• Ticket Priority Indicate the urgency or criticality—Low, Medium, High, or Critical.

Set the Objective

Choose the goal of the ticket. This helps OneLens customize the form to your use case:

• Resource Change You're making changes to one or more specific AWS resources.

• Service Change You're altering configurations or behavior at a broader service level.

• Others You're documenting an activity or change that doesn't fall into the above categories.

Provide Input Details

The fields you fill depend on your selected objective:

• For Resource Change

  This option is meant for resource-specific optimizations or updates.

  • Resource Information Enter the resource ID or ARN manually. You also can upload a file (CSV, JSON, or TXT).

  

• For Service Change

  Use this when you’re suggesting configuration or usage-level adjustments across an entire service (e.g., changing lifecycle rules across all S3 buckets).

  You’ll need to enter:

  • Account

  • Region (Optional)

  • Service

  
• For Others

  This category is for general or strategic recommendations that don’t directly modify a specific resource or service setting.

• You’ll still need to provide: Account, along with Region and Service details which both are optional.

  In addition, you’ll be asked to enter:

  • Usage Information Describe any usage patterns, cost observations, or operational behaviors that led to this ticket. This helps provide context for analysis and tracking.

Add a Recommendation

Describe the change you're proposing. Be clear, concise, and actionable. This serves as a reference for what needs to be done and why.

Assess the Impact

Help others understand the effort and implications by filling in the impact details:

• Change Type: Classify the nature of the change—like cost optimization, re-architecture, scale-up/down, etc.

• Optional Attributes (fill in if relevant):

  • Effort: Low / Medium / High

  • Risk: Low / Medium / High

  • Impact on Performance: State whether the change might improve or degrade performance.

  • Downtime Required (hrs): Estimate downtime, if any.

  • Compatibility Issues: Flag any integration or compatibility concerns.

  

Estimate Potential Savings

If the change has a financial benefit, enter the expected savings value. While OneLens won’t track this automatically, the value can help you prioritize the ticket internally.

Complete the Ticket

Finish setting up your custom ticket with final details:

• Assign Owner: Choose the user responsible for implementing the change.

• Due Date: Set a target date for resolution.

• Reason for Change: Share the motivation—cost reduction, compliance, performance, or operational improvement.

• Supported Documents: Attach up to 10 relevant files (2MB each), such as logs, architecture diagrams, cost assessments, or internal approvals.