Skip to content
Gallery
nytgames
CreativeTech Wiki (internal)
creativeTECH Wiki
Share
Explore
Processes

icon picker
CreativeTech Guide for Bug Triage and Project Prioritization

Follow this guide for how manage the priorities of CreativeTech Bug and Project requests.
A priority will be added to every Jira ticket. There may be special cases where the priority level will contradict the following guide. Priorities are set at the discretion of the PM, so pay attention to the priority levels and order of tasks.
If you have doubts or concerns about your priorities or which order you should do things, please ask your manager or PM for help. This document will evolve to clarify our team priorities.
DEVELOPERS: Do all BLOCKER and CRITICAL bugs at the beginning of Sprint. Get them out of the way.

Priority Planning

Issue Type
Issue Description
Priority
1
BUG
Broken unit or template, critical
Blocker
2
BUG
Event Tracker or other important issues
Critical
3
STORY
Planned bespoke Flexes and/or Paid Posts
High
4
BUG
Broken unit, non-critical
High
5
STORY
AS/WF/M assistance, urgent
High
6
STORY
Planned Bug/ET remediations
Medium
7
STORY
Planned internal project
Medium
8
STORY
AS/WF/M assistance, non-urgent
Medium
9
STORY
Sprint Spike/Special Requests
Low
There are no rows in this table
⁠

JIRA Priorities Definitions

Priority
Priority Definition
1
Blocker
Remediate Immediately
2
Critical
Remediate within Sprint, prioritize and CANNOT carry over to next Sprint
3
High
Remediate within Sprint, prioritize and CAN carry over to next Sprint
4
Medium
Schedule remediation for within 2-3 Sprints
5
Low
Schedule remediation
There are no rows in this table
⁠

Notes

AS/WF/M = AdSolutions/Webflow/Marketing

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.