Closed Bug 621088 Opened 15 years ago Closed 15 years ago

Change URL structure to support separate feedback tracks

Categories

(Input :: General, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Assigned: wenzel)

References

()

Details

(Whiteboard: NOTE: Nightly users, read comment 16.)

Attachments

(1 file, 1 obsolete file)

STR: 1. Load http://input.stage.mozilla.com/en-US/feedback with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9pre) Gecko/20101222 Firefox/4.0b9pre (Note: here, you'll get redirected to http://input.stage.mozilla.com/en-US/feedback/beta) 2. Click on either Happy or Sad (http://input.stage.mozilla.com/en-US/feedback/happy or http://input.stage.mozilla.com/en-US/feedback/sad) Actual: Keep getting redirected to /beta: 22:14:50.140: Network: GET http://input.stage.mozilla.com/en-US/feedback/sad [HTTP/1.1 302 FOUND 1512ms] 22:14:51.707: Network: GET http://input.stage.mozilla.com/en-US/feedback/beta [HTTP/1.1 200 OK 96ms] Expected: Probably should let me submit feedback using Minefield, or, if not, tell me to download the latest beta
Flags: in-testsuite?
Flags: in-litmus?
Ah, sorry; this is just bug 615729, isn't it?
Over to Aakash for a product decision: This is currently expected behavior (ergo, invalid). If a user uses a non-stable version (read: alpha, beta) and tries to visit the stable feedback pages, they get forwarded to the beta feedback pages.
Assignee: nobody → mozaakash
Ah, fun! If we want the correct user experience, then offering the /download page is the right way to go since we're only allowing for feedback in betas and stable versions of firefox. With that said...Stephen, does this approach hamper testing from QA at all? If so, we may want to look into adding something into the release checklist to better our processes around testing submission-related features for now in the future.
Aakash: Can you come up with a URL/user agent flow chart? It is currently expected that newer UAs get to see the feedback page (mostly, so that people on 4.0b9pre can leave feedback for 4.0b8). We can implement changes to the way it works after we come up with a comprehensive chart that we can point people to who think it is misbehaving.
Summary: Always redirected to /beta, using Minefield; unable to submit feedback → What kind of feedback should Nightly users be allowed to submit?
Aye, will do.
Nah, this doesn't adversely affect QA from testing, other than it'd be good to have the user-agent cases/flow spelled out (as Fred suggested in another bug).
Why not make /sad redirect to an alternative page if the version is more recent than stable? Said page might give a basic how-to for QA Companion.
Attached file url charts for input 3.0 (obsolete) —
Here's the chart for URLs and build types for Firefox. Feedback and questions welcome.
I have a few comments: - http://www.comicsanscriminal.com/ (no offense ;) ) - So we're not allowing any feedback from nightlies anymore? That makes me a little sad, but I guess that's consistent with us splitting up feedback intro three tracks. - I think forwarding latest beta builds from feedback to beta/download is wrong. They already have the latest beta build. If anything we should forward them to the beta feedback page. Same for latest mobile betas. - What's a "candidate for release" for a beta version? Isn't that a nightly?
Blocks: 620177
Priority: -- → P1
Attachment #499793 - Attachment is obsolete: true
Assignee: mozaakash → fwenzel
Aakash: After we talked yesterday, I think we decided on putting release feedback under: /release/feedback. Is that right? This would mean we'd need to change our URL structure some more and put the beta dashboard under /beta. We'd then add several intelligent redirects, from /feedback to /beta/feedback and /release/feedback, based on the UA, for example.
Summary: What kind of feedback should Nightly users be allowed to submit? → Change URL structure to support separate feedback tracks
Yep, thats right: /release/feedback /beta/feedback /nightly/feedback ...etc.
This is ready to roll: https://github.com/fwenzel/reporter/compare/master...url-structure-621088 Dave Dash: r? This moves all current pages (except for the single opinion page) under /beta, and the new feedback pages under /release/feedback. This makes room in the namespace for new dashboards etc. I also changed (and tested) the UA detection on the feedback pages, according to the chart in comment 10.
Status: NEW → ASSIGNED
Thanks for the review. I landed this here: https://github.com/fwenzel/reporter/commit/e2e12c8
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified
Status: RESOLVED → VERIFIED
Summary: Firefox Input version 3.x currently supports feedback submissions for release and beta versions only. Nightly versions of Firefox cannot leave feedback until support is added in Firefox Input versions 4.x.
Whiteboard: NOTE: Nightly users, read comment 16.
Component: Input → General
Product: Webtools → Input
Adding back the in-testsuite and in-litmus flags that were mistakenly removed.
Flags: in-testsuite?
Flags: in-litmus?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: