![]() In our example, we define these inputs in the Fields tab here. Your issue tracker issue list should sort issues by type. So if you're a PM who needs to manage a massive project, you place it in an epic, broken down into stories, tasks, and sub-tasks. "Epics" help team leads to manage the user journey and bucket-related tasks, while "user stories" are requests and needs in a customer's user journey. ![]() Then, the issues' type is listed, whether it's a bug, new feature, task, sub-task, story, or epic, which is an issue ticket that represents an overarching project that is broken down into specific tasks which are called user stories. Each ticket also has its own ID key, which can be defined by us, or by the ticketing software we use. A chart at the top shows resolver availability so managers know whose schedule is the most open to assign new issues. Reporters can either be internal team members or external customers who experience issues. To make ours, we started by making an issue list to track open tickets, then divided that list into a reporter section for whoever opens the ticket and a resolver section for whoever is assigned the ticket. This is an Issue Tracker spreadsheet template we created and is meant to complement whatever issue tracker software system you use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |