Create Tickets in Jira

Creating Clear Jira Tickets: How We Communicate, What to Fill In, and Why It Matters This video demonstrates how Jira tickets should be created and structured. The video covers: Ticket Types: When to choose Bug or a Task, and what each type is typically used for. - Bug: Something is not working as expected. The ticket explains where the issue occurs, what currently happens, what should happen, and how to reproduce it. Screenshots or videos are strongly recommended. - Task: A non-code activity, such as configuration, setup, research, or administrative steps. Tasks usually don’t require UI changes or new features. Required Fields: A good ticket is clear, complete, and easy for anyone to understand without extra explanation. It includes: - Title: Precise and meaningful at first glance. - Motivation: Why this ticket is needed and who benefits. - Goal / Expected Result: What should happen after the work is done, written as testable “acceptance criteria”. - Context: Screenshots, links, examples, or steps to reproduce (for bugs). A good ticket contains enough information that a developer, who has never seen the issue before, can understand the problem and deliver the correct solution. Priorities: What priority levels mean, how they are used in planning, and when an issue should be marked as urgent. If in doubt, this can also be managed by a PM. - Blocker: Core functionality unusable; immediate fix. - Critical: Major feature broken; high urgency. - Major: Noticeable issue; important but not urgent. - Minor: Small or cosmetic issue; low impact. Assignee: Assign the ticket to a Projectmanager.