Contact usSign up
How Do I Create a New Task or Ticket?

How Do I Create a New Task or Ticket?

Generating summary...
This response is generated by AI. AI can make mistakes.

Overview

Creating a work item in EVA means defining: who the work belongs to, what the scope is, what the urgency is, and who owns execution. EVA uses structured fields so tasks remain clear later, even when multiple teams collaborate on the same item. The most important decision point during creation is selecting the Task Type, because it drives classification and routing.

Step 1: Click “Create New”

Article image

Click “Create New” to open the form used to create a new work item. This same flow supports creating both Tasks and Tickets, since classification is automatic.

Step 2: Select the Client

Article image

In the Client field, select the customer context. The Client field supports selecting:

  • Account
  • Project
  • Subscription

This ensures the work item is linked to the right customer environment.

Step 3: Select the Store (if applicable)

Article image

In the Store field, choose the store linked to the selected account. This connects work to the correct store environment and enables store-related scoping in later fields.

Step 4: Select Product context (Brand / Tag / ASIN / SKU)

Article image

In the Product field, you can select values such as:

  • Brand
  • Tag
  • ASIN
  • SKU

This field supports multi-select and is used to connect the work item to specific product entities. It is especially useful when the task relates to a defined set of products rather than a general operational request.

Step 5: Select Type (Task Type)

Article image

In the Type field, select the type of work you are creating. This selection is critical because:

  • The item’s Task vs Ticket designation is determined automatically from this value.
  • The Responsible Team is assigned automatically based on this value.

This means the Type field is the routing driver of the entire system.

Step 6: Add a clear Title and Description

Article image
  • Title should be short and descriptive so the task is recognizable in Kanban and Table views.
  • Description should include the full explanation of what needs to be done, especially when the work requires context or collaboration.

Because tasks can be reassigned or monitored by Watchers, these fields should be written to remain understandable without verbal handoff.

Step 7: Add To-Do’s to structure execution

Article image

Use To-Do’s to break the task into smaller actionable steps. This helps execution remain structured, especially for multi-step operational workflows.

Step 8: Set Priority and ownership

Article image

Define urgency and responsibility using:

  • Priority: Medium / High
  • Assignee: the single person responsible for completing the task
  • Watchers: additional users who follow or monitor the task

The Assignee field ensures ownership is clear. The Watchers field ensures visibility for stakeholders who need to track progress.

Step 9: Add Attachments

Article image

Use Attachments to upload files and documents related to the work item. This keeps operational evidence and references stored inside the same task record rather than split across systems.

Step 10: Set due dates, ETA, and recurrence

Article image

Define timeline and scheduling controls:

  • Due Date: the target date by which the task should be completed
  • Recurrence Options: defines how often the task will be automatically reopened

These fields allow both one-time work and recurring workflows to be managed consistently.

Step 11: Save the item

Article image

After completing the form, save the work item, by clicking Create button. The new Task or Ticket will appear immediately in the Tasks Overview in the currently selected scope.