team based oops summaries should use the infestation team information to better group oopses
Bug #592355 reported by Diogo Matsubara
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-oops-tools | Triaged | Low | Unassigned | ||
Bug Description
This is an idea from Gary:
Team based summaries should have two sections, one with infestations only for the specific team and another with oops reports with the same team but where infestations have a different team value.
Something like:
<gary_poster> self.errors = self.errors.
<gary_poster> self.errors = self.errors.
infestation_
| Changed in oops-tools: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| affects: | oops-tools → python-oops-tools |
To post a comment you must log in.
I'm not sure this is valid with our now flat structure, but perhaps other folk will want it.