That your product team member can understand.
Overview: As a BA or PO/PM you need to write ticket description that can easily be understood by your team member, your goal is to have them to ask you ACs (acceptance criteria) as less as possible and that is saving your and their time (as time is a valuable resource).
As a PM at several companies, I have learnt and filtered down the best way to write a ticket based on my reference, a few bullet points below:
- Issue type: Wisely choosing your type, you can learn about issue type here https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/
- Summary (name of the ticket): it needs to be as precise as possible, a good name or summary can bring the idea to the user as quick as possible, this is important for prioritizing the priority status.
- Description: This is where you explain to the asignee or anyone whose work relates to this ticket about what this ticket is about, the structure in my opinion can be broken down into 2 part:
- Current state (optional):
- User story (depends):
- What to do (optional):
- Acceptance criteria:
- Technical ACs:
- UX ACs:
- UI ACs: