Closed Bug 121111 Opened 23 years ago Closed 11 years ago

longlist urls aren't portable

Categories

(Bugzilla :: Query/Bug List, enhancement, P4)

Product:
Bugzilla
Component:
Query/Bug List
Version:
2.15
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 118805

People

(Reporter: timeless, Unassigned)

References

(
URL
)

Details

longlist urls should be portable, preferably in some get format.
Priority: -- → P4
Target Milestone: --- → Bugzilla 2.20
Ummh, what does portability mean in this context? Simply that the url would contain the query? Is there any reason why hitting the longlist button shouldn't be submitted as a get rather than a post? Would that fix this issue?
We can't use a GET, because the resulting url ends up too long if there are more than just a few bugs.
Ok. Three thoughts. 1. to allow people to pass around a longlist document and have it regenerate a similar list, we could provide a button 'refresh list' which resubmits the query that was used to generate the list to longlist. 2. why can't longlist behave like bug_list and take a query as input? 3. the symptom i experienced was that the comment references were totally useless which could be fixed by making long list comment references prefix show_bug.cgi?id=<> to the hash ref.
Assignee: endico → nobody
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: nobody → query-and-buglist
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
fwiw comment 3 point 3 is bug 121112
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.