Label | Open Bugs with Label | Meaning | Relevency |
---|---|---|---|
a11y | Bugs related to accessibility | ||
bulk_email | Issues related to bulk email | ||
browser | Issues that are specific to browsers (i.e. IE) | ||
byte-sized | Small issues, great for people new to the platform | ||
cause-unknown | We don't know what's causing this issue | ||
content-caused | These issues are caused by authored content | ||
Escalation | Bugs handled by the Escalation team | ||
escalation-triaged | Bugs that are triaged by the Escalation team. | ||
edx.org | Issues specific to edx's instance of openedx | ||
escape | "Escaped defect": a bug that's reported to us by a third party | ||
export | Bugs related to course export | ||
external_contribution | Bugs related to third-party contributors | ||
flaky_test | Flaky tests that should be made less flaky | ||
front_end | Front end bugs | ||
graders | related to external graders | ||
grading | related to grading courses | ||
IE | Internet Explorer | ||
hotfix | Issues that have been hotfixed | ||
i18n | Issues related to internationalization | ||
import | Issues related to import | ||
instructor-dashboard | Issues related to the instructor dashboard | ||
instructor_task | Issues related to executing tasks from the instructor dashboard (bulk email, etc) | ||
javascript | Bugs caused by javascript | ||
Monitoring | Bugs that we need more monitoring to fix | ||
logs | Issues picked from the splunk logs | ||
matlab | Issues related to matlab integration | ||
needs-information | Issues that need more information before they can be acted on | ||
no_escalation | Issues NOT supposed to picked by escalation team | ||
PM | Issues related by the PM team | ||
opaque-keys | Issues related to opaque keys | ||
Issues related to the pdf reader | |||
performance | Issues related to site performance | ||
progress-page | Issues related to the progress page | ||
RCA | Bug reports that come out of RCAs | ||
UI | Issues related to user interface | ||
queueing | Issues where instructor tasks get stuck in queueing | ||
scaling | Issues related to scaling | ||
transcripts | Issues related to video transcripts | ||
unicode | Unicode errors | ||
video | Video module errors | ||
wiki | Django wiki bugs | ||
xml | Bugs related to XML authoring – in or out of studio | ||
xqueue | Bugs related to xqueue | ||
xqwatcher | Bugs related to xqwatcher | ||
a11y wcag 2.1 cleanup tasks | Accessibility audit tasks | ||
Configuration | Identify which CR's/Prods required no code and could have been prevented by non-engineering expertise | ||
Escalated | Auto-applied when a CR ticket is escalated. Used to track escalated CRs in reporting since status reporting is finicky in Jira | ||
Escalation-fallout | Remediation work to clean up potential problems from rapid decision-making during escalations | ||
Expedite | Flag to identify lower priority issues that if not complete by a certain timeline will become highly escalated. | ||
Grooming | Labels for tickets pending review at the next S&E Grooming session. | ||
integration | Third Party Integration requests | ||
Library Upgrades | Upgrading system libraries/dependencies in order to keep code up to date and secure | ||
Pending_Review | Tickets in Blocked or generally pending product or eng lead direction | ||
Reopened | Auto-applied to CR's that are reopened. Used to report on situations where we're potentially resolving issue pre-maturely, or not communicating the resolution well enough. | ||
Root-Cause | Identifies a ticket where a acute symptom was addressed but the root cause is still unknown and could happen again | ||
Technical-Debt | work that would improve ability for other teams to code but has low priority | ||
Trend | Issues that represent growing or persistent trend with sustained features. Current examples: Archived-courses, Certificates, Entitlements, Grading, learner-record, ORA, Prerequisites, Proctoring, Masquerade, roles, dates |