Open Bug 1246903 Opened 8 years ago Updated 2 years ago

Add a 'go to build...' action to other menu

Categories

(Testing :: mozregression, defect)

defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: yfdyh000, Unassigned)

References

(Depends on 1 open bug)

Details

For quick access to a suspected point, instead of gradually progressive to it. The trouble is more evident after ApproxPersistChooser emergence.


Will better: Reuse the mid-build dialog, mark and allow only show the downloaded packages, like a checkbox on the dialog.


One difficulty (possibility): Allows to enter a suspect build by any format (date/buildid/...), and any branch (repo), and don't break the workflow.

For example, when I found out a range in m-c, I view the push_log, I found a suspiciou commit in inbound branch. I should be able to directly test its surroundings (nearby builds in inbound branch), and don't break the workflow (if the both before and after builds is bad/good unity, return to the previous flow to continue).
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.