Closed
Bug 94505
Opened 24 years ago
Closed 7 years ago
After voting for a bug, there is no 'back to bug X' link (cannot return to bug X, missing link) [was: ...should there be a 'back to bug X' link?]
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P4)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bugzilla, Unassigned)
References
Details
Attachments
(1 obsolete file)
There isn't at the moment
I've got a simple patch to do this, which I'll attach post-2.14, which just
passes the bugid through showvotes.cgi, and onto doeditvotes.cgi, so they can
both provide 'back to bug' links.
Is this the best way to do 'back to bug' links though?
Might it be better to have some sort of generic system for storing the last bug
someone visited (as a cookie set in show_bug.cgi?), and then there could be a
'back to bug' link in the footer, or perhaps just before the footer, on each
bugzilla page?
Comment 3•24 years ago
|
||
I'd rather not do it via cookie. We're running into problems with the cookie
method already with the last bug list you viewed because people tend to view
multiple buglists at once in different browser windows, and the cookie is global.
Comment 4•24 years ago
|
||
->New product Bugzilla
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.12 → 2.12
Comment 5•24 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut. Thus this is being retargetted at 2.18. If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 6•24 years ago
|
||
Submit now goes back to the 'edit votes' page - is this now fixed?
Comment 7•22 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18.
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 8•21 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged
enhancement that hasn't already landed is being pushed out. If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Updated•19 years ago
|
OS: SunOS → All
Hardware: Sun → All
Comment 9•19 years ago
|
||
Attachment #237764 -
Flags: review?
Comment 10•19 years ago
|
||
Comment on attachment 237764 [details] [diff] [review]
patch for tip
>Index: template/en/default/bug/votes/list-for-user.html.tmpl
>+[% IF products.size %]
>+ <p>
>+ [% FOREACH bug = product.bugs %]
First of all, "product" doesn't exist ("products" does, though). Then, I don't want to have a full list of URLs when having several bugs displayed in the page. I don't know which UI GavinS exactly had in mind, but I don't like this solution. I would tend to only take the first part of the patch, when viewing votes for a given bug.
Attachment #237764 -
Flags: review? → review-
Updated•19 years ago
|
Attachment #237764 -
Attachment is obsolete: true
Comment 11•17 years ago
|
||
Each time I vote for a bug it's a pain to get back to the bug for which I voted. In other words, for those people who still bother to vote at all, the presence of this bug has been making it unnecessarily hard ever since 2001.
Comment 12•16 years ago
|
||
This is not an enhancement, it's a bug (changed summary accordingly). After voting, user won't have any obvious way of returning to the bug for which he voted. Using the back button isn't an acceptable workaround as most users will avoid this because normally for good reason you don't go back across input forms that you have just posted, plus you'd have to press back button up to 5 times to get back to your bug when you logged in just before voting for a particular bug. When you get back to the bug, you'll see the old version of the bug's page unless you refresh. Looking for the bug you just changed in between all your other bugs and then click on the bug's link is not an alternative, either, as soon as user has more than a couple of bugs he voted for.
Severity: enhancement → normal
Summary: After voting for a bug, should there be a 'back to bug X' link? → After voting for a bug, there is no 'back to bug X' link (cannot return to bug X, missing link) [was: ...should there be a 'back to bug X' link?]
Version: 2.12 → unspecified
Comment 14•11 years ago
|
||
Shouldn't the UI for voting be reworked, so the user just has to make one click to vote for a bug like it's done in other bug tracking systems like GitHub or Google Code?
Showing an overview of bugs you voted on is just an additional feature and could then be accessed differently, e.g. via the preferences as described in bug 577849 or within the user's dashboard.
Sebastian
Comment 15•10 years ago
|
||
If bug 69754 gets implemented, there is probably no need anymore for this feature.
Sebastian
Depends on: 69754
Updated•10 years ago
|
Blocks: bz-voting-ux
Comment 16•8 years ago
|
||
@Byron Jones, Thank you for mentioning it's a duplicate.
Comment 17•7 years ago
|
||
The voting functionality will be replaced with emoji comment reactions in the near future.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•