Closed Bug 1102837 Opened 10 years ago Closed 10 years ago

Add regression test for direct calling of a blocked contact

Categories

(Hello (Loop) :: Client, defect, P3)

defect
Points:
3

Tracking

(firefox35-, firefox36-)

RESOLVED WONTFIX
Tracking Status
firefox35 - ---
firefox36 - ---
backlog tech-debt

People

(Reporter: mikedeboer, Unassigned)

References

Details

(Whiteboard: [tech-debt])

Bug 1102806 was about fixing a regression where somehow this feature was not migrated to LoopCalls.jsm. IF we had a unit test in place, this wouldn't have regressed. Let's add one this time.
Flags: qe-verify-
Flags: needinfo?(mmucci)
Flags: firefox-backlog+
Added to IT 36.3
Flags: needinfo?(mmucci)
backlog: --- → Fx35+
Iteration: 36.3 → 37.1
[Tracking Requested - why for this release]: [Tracking Requested - why for this release]: We want to add this test and uplift it to Fx36 and Fx35 to prevent future regressions.
Hi Mike -- Are you planning to finish off this bug this week?
Flags: needinfo?(mdeboer)
Not tracking. We won't block the release for that.
Iteration: 37.1 → 37.2
I'd really like this in fx35, but as Sylvestre says we won't block release for this.
Priority: P1 → P2
Not planning to work on this now, maybe next week.
Flags: needinfo?(mdeboer)
Assignee: mdeboer → nobody
Iteration: 37.2 → ---
Flags: needinfo?(mmucci)
Removed from IT 37.2
Status: ASSIGNED → NEW
Flags: needinfo?(mmucci)
I would love to get this fixed and uplifted into Fx36 to protect us against regressions.
backlog: Fx35+ → Fx36+
backlog: Fx36+ → Fx38+
Whiteboard: [tech-debt]
Assignee: nobody → rgauthier
backlog: Fx38+ → tech-debt
Priority: P2 → P3
Priority: P3 → P4
accidentally changed priority- sorry for bugmail
Priority: P4 → P3
Rank: 37
Assignee: rgauthier → nobody
We are currently reworking the Loop "user journey" (bug 1209713) and as part of this direct calls and contacts are being removed. Therefore closing direct call related bugs as wontfix. Tracking id: directcallclosing
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.