Logging tasks in Yantra

What type of task is it?

You will find the following choices when you log a task in Yantra:

  • Issue
  • New report functionality
  • Bigger project/new implementation

Process for issues, small tasks:

Create a new task in Yantra. Give as much information as possible about what the issue is/what you require to be done.

What to include:

  • The process that you have followed. More information is best! As much detail as possible. Assume that the consultant picking up the ticket has no prior experience of the environment (but knows your CRM)
  • Screenshots. Quick. Easy. Efficient.
  • Error messages – text or screenshots.
  • URLs – specific links of where the behavior is occurring (or should occur).
  • Screen recordings of specific scenarios. It allows us to easily replicate and then investigate.
  • Sample IDs to use for testing.
  • Who the user is logged in as.
  • Which browser are you using.

Provide acceptance criteria for completion. It may be obvious, “fix it!

  1. When you have submitted a task, a default one hour investigation time will apply (unless you have specified differently). Usually, we would expect around an hour is sufficient. We can then inform you of our findings and how long (if required) it will take to complete the task and ask for your approval. In some scenarios our investigation will find that it is a product issue, in which case this should be logged with the product provider.
  2. You sign off on an estimate if you want to go ahead with the proposed work.
  3. We undertake the work. Before we get this back to you, we will test. If we take longer than has been estimated, we will come back to you for approval of more time and an explanation of why more is required. Please note, on occasion we may continue with work before requesting more time due to time sensitivity.
  4. We expect testing to occur on both sides. Sometimes this is iterative, so it may go back and forth depending on the issue. We will aim to have it right the first time!
  5. Once accepted by the client – this is completed and we will close ticket. If we do not hear from you in a reasonable period of time we will consider it complete.

Process for bigger/project pieces of work/new developments (c.20 hour projects)

For bigger pieces of work, you may want to consider contacting your account manager directly to discuss any upcoming work you may require.

We would need to know:

A clear scope of what you require to be developed or changed by Zentso.

What we’d like to see:

  • Business context (the purpose, how it came about, why!)
  • Desired outcome
  • Dependencies between the task and other tasks – if known
  • Enough information to assess the risk before starting the work – if known

Please also provide timeframes for when the work is required by (if applicable).

For larger pieces of work, Zentso will spend some time to propose a solution and an estimate how long it will take to complete this. The amount of time to do this will depend on the size of the project/request itself. Work required to analyse the level of effort required is billable.

Please do not:

  • Email us with tickets – use Yantra, unless it is an emergency!
  • Conflate tickets
  • Duplicate tickets
  • Give us limited information