# Ticket Templates

There is often a miscommunication or misunderstanding between product and engineering.  Product managers may struggle to explain exactly what it is they want or they may not include all the edge cases for their feature.  On the other side of that, engineers might not be able to fully explain details that they require or they don't have enough business context for their task.

This can be resolved by having clear tickets or chunks of work that the engineer can execute.  This requires both product and engineering to be in sync and to have a common standard of documentation.

I will be explaining my templates in the context of Jira as it is the only project management software I have used. However, these templates and principles though be extendable to any form of task tracking software.

{% hint style="info" %}
Refer to [here](https://support.atlassian.com/jira-software-cloud/docs/what-is-an-issue/) for more details on Jira issues
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.roblkdeboer.com/product-management/ticket-templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.