=== zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has left #ubuntu-meeting ["Leaving"] === blahrus [~blahrus@12-223-50-121.client.insightbb.com] has joined #ubuntu-meeting === jiyuu0 [~jiyuu0@219.95.241.41] has joined #ubuntu-meeting === ogra [~ogra@p5089F7A6.dip.t-dialin.net] has joined #ubuntu-meeting === jdthood [jdthood@x096.decis.nl] has joined #ubuntu-meeting === |QuaD-_ [~QuaD@beac872-0b01-dhcp144.bu.edu] has left #ubuntu-meeting [] === pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-meeting === mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting === pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting [] === jane_ [~JaneW@wbs-146-176-233.telkomadsl.co.za] has joined #ubuntu-meeting === JaneW [~JaneW@wbs-146-176-233.telkomadsl.co.za] has left #ubuntu-meeting ["Leaving"] === simira [~simira@56.80-202-210.nextgentel.com] has joined #ubuntu-meeting === sladen_ [paul@starsky.19inch.net] has joined #ubuntu-meeting === sladen_ [paul@starsky.19inch.net] has joined #ubuntu-meeting === sladen [paul@starsky.19inch.net] has joined #ubuntu-meeting === sladen_ [paul@starsky.19inch.net] has joined #ubuntu-meeting === sladen [paul@starsky.19inch.net] has joined #ubuntu-meeting === pitti [~martin@box79162.elkhouse.de] has joined #ubuntu-meeting === pitti [~martin@box79162.elkhouse.de] has left #ubuntu-meeting [] === Simira [~Simira@56.80-202-210.nextgentel.com] has joined #ubuntu-meeting === doko [~doko___@dsl-084-059-061-070.arcor-ip.net] has joined #ubuntu-meeting === dato [~adeodato@84-120-77-228.onocable.ono.com] has joined #ubuntu-meeting === thom [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting === dholbach [~daniel@td9091a81.pool.terralink.de] has joined #ubuntu-meeting === jiyuu0 [~jiyuu0@219.94.81.23] has joined #ubuntu-meeting === JanC [~janc@JanC.member.lugwv] has joined #ubuntu-meeting === thom_ [~thom@amnesiac.heapspace.net] has joined #ubuntu-meeting === Seveaz [~seveas@seveas.demon.nl] has joined #ubuntu-meeting === bradb [~bradb@MTL-ppp-146985.qc.sympatico.ca] has joined #ubuntu-meeting === robitaille [~robitaill@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting [09:59] MOTU Malone meeting in 2 mins! [10:00] ding ding ding! [10:00] right, who's here then? [10:00] woohoo!" [10:00] dong dong dong [10:00] (that's participating in the Malone MOTU meeting) === BjornT [~bjorn@MTL-ppp-146985.qc.sympatico.ca] has joined #ubuntu-meeting [10:00] hey BjornT [10:00] hi [10:01] hi [10:01] robitaille, hey [10:01] ogra, robitaille, BjornT, dholbach. who else is in for this meeting? === Treenaks shows up [10:01] shall we use http://wiki.ubuntu.com/MaloneUniverseWishList for a general overview? [10:01] dholbach: that's what i'm looking at right now [10:02] right, let's get started then [10:02] there are at least two things on the agenda [10:02] 1. a report from the field (i.e. you guys, users of Malone) [10:03] 2. a plan forward to try to give us an idea of the most critical issues that need solving soonest === herve [~hcauwelie@ip-3.net-81-220-179.nice.rev.numericable.fr] has joined #ubuntu-meeting [10:03] are there other things you guys want to add? [10:03] no... fine with me [10:04] morning [10:04] hey ajmitch_ [10:04] ok...we'll try and keep this down to half an hour or less. all we need is enough to move forward for the next week or two, based on what's making it hurt the most for you guys [10:05] so, #1 then, who wants to give me a summary of MOTU's experience on malone up to now? :) [10:05] how's it been going? have you been using it a lot? [10:05] is anyone saying they absolutely can /not/ use Malone right now on the MOTU team, because feature XYZ is missing? [10:06] I've used it two weeks ago [10:06] some "views" on bugs dont work [10:06] I managed to go throught it === seb128 [~seb128@ANancy-151-1-34-31.w83-196.abo.wanadoo.fr] has joined #ubuntu-meeting [10:06] seb128! [10:06] thanks seb128 [10:06] hi [10:07] but found several traps [10:07] salut [10:07] sorry I've forgotten [10:07] hi seb128 [10:07] so, what's up? :) [10:07] all the "views" on the bug list show the same list [10:07] bradb, searching in distribution bugs doesnt work, thats one of the most essential things i think [10:07] 8 pages of new or accepted bugs, it looks like...good to see that some people are using it then... [10:07] ogra: yep, i'm fixing that right this minute :) [10:07] yeah :) [10:08] namely unassigned . my todo list . critical . submitted by me [10:08] huge cleanup/fixing [10:08] dholbach: yep, i'm fixing those links right now too [10:08] dholbach: that uses the search, no? [10:08] yep [10:08] looks like [10:08] yeah [10:09] bradb, one of the main problem to me, is you have to click many times to navigate throught malone [10:09] so don't worry about that. that'll be done as soon as i finish it. it's my top priority right now. [10:09] wait, one sec. [10:09] have you guys got your team all setup properly now? [10:09] "back to list" would be great, in accordance to what herve said [10:09] making teams isnt your "resort", bradb, right? [10:09] with everybody in the team that needs to be in the team and a sane email address to which notifications for the team will be sent? [10:09] nope, its ours... [10:10] ogra: launchpad-wise of course [10:10] ogra: interface-wise === mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting [10:10] sure, but i admit i was lazy and dint add everyone to the MOTU team [10:10] if they haven't whined, perhaps it doesn't matter [10:10] heh [10:10] it does, for us ;) [10:11] i wonder if you guys want a mailing list specific to universe bugs [10:11] how can i set a mail adress for a team? [10:11] which could then of course be the email of the team in Malone [10:11] that's ubuntu-users, no? :-) [10:11] herve, no, thats the past ;) [10:11] herve: if it isn't, then that should be the email address of the team...but eh, you probably don't want that. :) [10:11] if it *is*, i meant [10:12] is this meeting a random suggestion mixed one? or is that a plan or something? [10:12] i can't see the mail adress thingie for a team [10:13] seb128: [10:13] [16:02] 1. a report from the field (i.e. you guys, users of Malone) [10:13] [16:03] 2. a plan forward to try to give us an idea of the most critical issues that need solving soonest [10:13] seb128: we currently name the most annoying things [10:13] k [10:13] the first thing i wanted to focus on was talking about how you're using Malone right now, including making sure you're setup correctly re: the MOTU team in Malone [10:14] dholbach, ogra: do you want to have a mailing list setup specifically for universe bugs? do you need one? [10:14] i used it to assign bugs to teams, closed some fixed bugs [10:14] - no way to get the lists of bug from the list of comments [10:14] - no way to edit the bug from the comments [10:14] - no way to comment when editing the bug [10:14] - no way to assign a bug when submitting it [10:14] that's my list :) [10:14] i guess it would be best now to have a ML [10:15] jdub has already planned some lists we will need [10:15] since we cant set up this list in malone itself for a team... [10:15] dholbach: was an MOTU bug list one of them? [10:15] seb128: did he mention ubuntu-bugs-universe? [10:15] ogra: Malone's not mailman, so no, you can't :) [10:16] then we'll need a list.. [10:16] ogra: you can set the email of the team though [10:16] bradb: where? [10:16] not on "edit team details" [10:16] bradb: i have the gnome team's page open right now === zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting [10:16] it might be something the owner has to do [10:16] i am the owner [10:17] i have the MOTU page open, there is no field for email (i'm the owner) [10:17] dholbach: nop, but was not an easy discussion :) [10:17] dholbach: it's not available to you in edit team details/ [10:17] nope [10:17] +addmail and +addemail didnt work, i tried that ;-) [10:17] heh [10:17] ugh === koke [~koke@adsl229-164.unizar.es] has joined #ubuntu-meeting [10:18] i'll look into this while the meeting continues [10:18] bradb, but launchpad has all our mailadresses.... [10:18] sure [10:18] there's a bit of a problem here to getting you guys useful notifications too... [10:19] we shuldnt need a team mailadress, even if its not mailman, it coud send to all members of the team [10:19] we need all the MOTU source packages to have the MOTU team set as maintainers, ATM :/ [10:19] ugh [10:19] 15000 packages.... [10:19] emails! :-) [10:19] bradb: how do we set the QA and assigned for a package? [10:20] can't we bounty someone to enter them all ? === tseng|work [~ccc27a01@sls-eb20p9.dca2.superb.net] has joined #ubuntu-meeting [10:20] thats a lot of typing and clicking :) [10:20] ogra: i'll make a note to talk to mark about this, so you guys can be properly setup to get sane notifications sent to an appropriate email address (or, possibly, addresses) [10:21] bradb: multiple adresses would be cool [10:21] anything else we need to cover about the logistics of you guys using Malone? [10:21] because we will have overlapping subsets of packages [10:21] (for point #1...before we get into the part about where malone sucks :) [10:21] anyone having problems logging in or getting their account sorted? [10:21] dude.. malone is totally shithouse [10:22] anyone here who's meant to use malone but hasn't yet? [10:22] (jk :P) [10:22] tseng|work: calm yourself a bit [10:22] for 43 people in here... it's a bit calm [10:22] ok, let's move on then :) [10:23] bradb: I haven't used it yet.. haven't had time [10:23] let's go through the biggest pains you guys are experiencing with Malone. i need enough feedback to guide BjornT and me for the next week or two, but no more [10:23] bradb, err, the bounty thing was a joke... [10:23] Treenaks: will you try it out this week perhaps? [10:23] bradb: is there any meeting scheduled about main maintainers/malone? [10:23] ogra: i know :) [10:23] bradb: uh, I could make some time this weekend [10:23] phew [10:23] ogra: talking to sabdfl about it wasn't a joke though :) [10:23] heh [10:23] ok [10:23] we really need to get that sorted for you guys, or you won't even get bug notifications [10:24] in some way shape or form [10:24] the search/assigned thing is the most important i think, a "back to list" would be VERY handy, that's how i feel === maskie [~maskie@196-30-108-163.uudial.uunet.co.za] has joined #ubuntu-meeting [10:24] cant you just script the import of a packagelist ? [10:24] seb128: not currently, but you can vent here :) === ajmitch_ hasn't used malone enough (assigning/entering) to complain any further than has been done ;) [10:24] ogra: they're already doing that, afaik [10:24] bradb: yeah, but that's too noisy I think :) [10:25] ah, ok [10:25] bradb: and we probably don't have the same concern as universe guys [10:25] ajmitch_: will you make a point of giving it a shot over the next week or so a bit? [10:25] seb128: tell us about your worries... :-) [10:25] seb128: you will be customer #1 for it === bradb is meaning to get back to seb128's list in one sec :) [10:25] yeah, I know ... but don't want to grab the focus [10:26] bradb: yes, I'll try & squeeze it in there [10:26] lol [10:26] that's a motu meeting [10:26] i noticed the other day when i was not logged in and tried to comment, then was told to log in... crash [10:26] not a desktop team one [10:26] no, that's a malone meeting? [10:26] ill try to verify that [10:26] seb128: you're too gracious :-) [10:26] good. /me makes a point of bugging Treenaks and ajmitch_ at the next meeting about what they like and don't like about Malone. [10:26] OK :) === ajmitch_ isn't meant to be at this meeting, meant to be at work at the moment! :) [10:27] Treenaks, ajmitch_: you're scratchpad is ready: http://wiki.ubuntu.com/MaloneUniverseWishList [10:27] seb128: you're the only one who's given specific feedback so far in this meeting about what sucks about Malone? [10:27] ok.. searching for "f-spot" on the ubuntu distro bugs page is not working also [10:27] sorry im not sure what are already "known issues" [10:28] thats one [10:28] bradb: dunno, I've not really read everything [10:28] I've completed my list [10:28] I've 6 points now :) [10:28] tseng|work: pretty much everything people tell me are problems we know about. :) the key is, what are the things /most/ hindering you guys? [10:28] let me know when that's time for that [10:28] bradb, searching! [10:28] well going to search there and having nothing happen [10:28] by package, people, status... [10:28] and clicking advanced and having it fail.. [10:28] herve: i already mentioned that i'm fixing that as we speak [10:29] thats pretty suck, i sthere osmewhere I can hav ea wokring saerch? [10:29] bradb, you mean advanced search like "what are all my pending upload bugs?" ? [10:29] gr lag [10:29] tseng|work, brain lag? :-) [10:29] herve: yeah, my next merge is what will fix that. [10:29] rock! [10:30] having 100 bugs/tasks per page would be great :-) [10:30] client lag, I cant see what im typing === herve stops whining for tonight :- [10:30] let's keep focussed here dudes. if noone has any specific problems to report then i'll throw the mic over to seb128 and see what's on his mind. [10:30] in 3 [10:30] 2 [10:30] well I think we are saying, if I cant search or get a page of my own bugs [10:30] bradb, [10:30] I'll never keep track of them [10:30] subscribing oneself easily [10:31] tseng|work: searching will be fixed asap [10:31] should I copy my list here? :) [10:31] without having to type its name each time [10:31] ok. [10:31] tseng|work: dude, i've already addressed that point :) let's keep moving forward here. [10:31] and being also to remove too [10:31] one sec, I just sort it [10:31] cool [10:31] herve: yes, good point [10:32] herve: but is it really critical? probably not. [10:32] bradb, time wasting? ok I'm picky :-) [10:32] bradb: what do you think about a "back to list" link? [10:32] navigation would be more important [10:32] i mean, you're the users, you tell me, but it doesn't seem to me that having to type one's name to sub to a bug is a critical issue for the time being, IMHO [10:32] like getting from a report back to the list [10:32] herve: yes, absolutely. the nav sucks. [10:33] another confusing thing [10:33] herve: ok, on that point (we'll get to you seb128...very soon.. :) [10:33] there are bugs and tasks with different numbers [10:33] herve: YES! [10:33] someone said #123 [10:33] and I was searching for non existent bug 123 :-) [10:34] i really, really, really need to convince sabdfl that virtually every Malone user has screamed about the problem of having two IDs for what the user thinks is the same thing [10:34] thus far, i've not been permitted to fix that in the way that i want, which is to completely hide the "task" ID altogether [10:34] herve: i'm glad you mention this though, because i log all IRC conversation, so it gives me more ammo for the sab :) [10:35] ok, so one thing [10:35] interesting that nobody's mentioned the assigned report yet [10:35] anyone even using that? === \sh [~shermann@server3.servereyes.de] has joined #ubuntu-meeting [10:36] don't remember it [10:36] that was about to be the next thing i set in my sights to fix, but it doesn't seem to be the thing users currently complain much about, because nobody even cares enough to use it, apparently [10:36] bradb: I've tried [10:36] all the "views" on the bug list show the same list --- namely unassigned . my todo list . critical . submitted by me [10:36] <\sh> g'evening [10:36] but until yesterday it crashed with a system error [10:36] and point 23 on the wiki page: "https://launchpad.ubuntu.com/malone/bugs/assigned?name= seems broken atm" [10:36] dholbach: that's part of the searching, and as i noted earlier, i'm fixing those links :) [10:37] i thought you were talking about this, when you said "assigned report" [10:37] yes, i think SteveA's done a fix to fix that bug in the assigned report [10:37] i've tried to use it [10:37] it worked at UDU [10:37] bradb, a wishlist: from any page, click the login link, log in, then you get redirected to the previous page [10:37] herve++ [10:38] yeah [10:38] but that's part of "navigation", i presume? [10:38] dholbach: that link worked for me just now [10:38] dholbach, navigation is a very global term [10:38] I would mean the breadcrumbs too [10:38] bradb: it gave me system errors [10:38] now it works again [10:39] herve: yep, very good point there too...the login has gotten quite a bit better lately (which you might have noticed if using LP a lot, but maybe not if you only use it a bit), but definitely has a bit of a way to go yet to work the way most people expect [10:39] herve: i know, but bradb acknowledged that "navigation sucks" (his words) [10:39] yes, my words :) [10:39] bradb: I have 9 things in a tomboy note about disturbing behaviours I've observed since 2 days ago [10:39] but, I think most are not *high* priority items [10:40] let's focus on high priority? [10:40] if they're minor things, you can email them to me: brad.bollenbach@ubuntu.com. [10:40] malone needs to be usuable soon [10:40] not to have a ton of cool features [10:40] fonts ! [10:40] *g* [10:40] :( [10:40] bradb, I checked my assigned page, the links seem to be some javascript... you should get tortured for that!! :-) [10:40] seb128: most are usability things but not as urgent as "search" [10:40] :D [10:40] seb128: go ahead with your list [10:40] i've taken notes of what you guys have said so far...does anyone have any other high priority items that we should discuss right now, or should i hand the mic to seb128? [10:41] ok, seb128, go for it [10:41] 1- no way to comment on the bug when you edit it [10:41] 2- clicking on bug from the list should open the bug description, not the bug edition [10:41] 3- no way to go from the comments to the bug edition? [10:41] 4- no way to go from the comments to the list of bugs? [10:41] 5- no way to assign a bug when submitting it [10:41] 6- don't send mail to the guy doing the change [10:41] 7- custom lists of bugs [10:41] 2++ :) [10:41] yep [10:41] seven points...gimme a minute to copy paste and absorb :) [10:41] let's take that by order maybe? [10:41] I had it as "- Bug list pointing to bugs, not tasks (or more info in tasks page)" [10:42] seb128: let's start by classifying them. we'll ignore for the moment the non-high-priority items, but i'll make note of them all the same, of course. [10:42] so #1 [10:42] medium-highish priority [10:43] because it's a pain to do an edit and then go back to the bug page to add a comment explaining your change [10:43] I've classed them by priority from my point [10:43] editing and commenting are the same action [10:43] when you change the properties of a bug you want to explain why [10:43] absolutely [10:44] when changing state it should be required [10:44] yep [10:44] you cant close a bug w/o a comment [10:44] i think it won't overtax users to have all of this on one page :-) [10:44] mpt might be doing some work on this at the moment, in trying to improve the whole too-many-clicks between bug and task pages, but i'll have to double check with him, and he's probably sleeping atm [10:44] k [10:45] ok, so, we agree #1 is fairly high priority, for both bug info and task info, right? [10:45] correct [10:45] ++ [10:45] ok, noted. #2 now. [10:45] hm [10:45] you want to view the comments before acting [10:45] for sure [10:45] 90% of the time [10:45] seb128: do you though? given that the description is editable. [10:46] yep [10:46] why? [10:46] because you want to see *all* the informations [10:46] before judging [10:46] we're intending for comments only to add information to explaining what the problem is. the ideal place to get the sum total of useful info about the bug should be the description, no? [10:46] hum [10:47] you need to fix people so [10:47] nobody update the description atm [10:47] and that's extra work for the maintainers [10:47] bradb ever looked at our/other distros bugzilla? im sure you have, there is a ton of debugging info going on [10:47] seb128: is it less work to read all the comments instead every time you look at the bug report? :) [10:47] or more info that wasnt (but should have been) in the summary [10:47] bradb: for sure yes [10:48] I just read the current comment [10:48] and I can scroll back without any action [10:48] to know everything about the bug [10:48] bradb, one thing before I leave, I can't mark bugs as duplicate [10:48] must go now, bye === herve [~hcauwelie@ip-3.net-81-220-179.nice.rev.numericable.fr] has left #ubuntu-meeting ["Leaving"] [10:48] heh, not that he's here anymore, but dups i've already got in SteveA's code review queue [10:49] ok, so back to point #2 [10:49] atm the description is not even usuable [10:49] it eats all the CRLF [10:49] so that's a mess [10:49] which doesn't help to work from the edit page :) [10:50] <\sh> well, for me, the status of malone is more a plain ticketing system like RT, then a bug maintaining tool. [10:50] yep, white-space: pre now! :) [10:50] seb128: it's only like that on the task page (it should look ok on the bug page), but stub might have fixed that. [10:50] he ported the bugfix from Zope 3 to our codebase last week to fix that, i think, but i'll have to double check === bradb makes a note [10:50] bradb: task page == edit, bug page == comments? [10:51] yeah [10:51] right [10:51] erm... why did the mail with my changes go to dilys@muse.19inch.net? [10:51] but you go on the task page from the list [10:51] which has the issue [10:51] dholbach: it's our IRC bot [10:51] oh cool [10:52] in which channel is it? [10:52] bradb: how do I edit the bug description? [10:52] seb128: so you'd prefer to, when looking the list of tasks, have to always do a second click to get to the page where you can change assignee, status, triage, etc? [10:53] yep [10:53] seb128: click on Edit Bug Details from the bug page [10:53] correct [10:53] ok [10:53] I want to read the comments before acting [10:53] ie: there is a new bug [10:53] the guy has opened it [10:53] and put 2 comments then [10:53] I want to know about the comments first [10:54] makes sense [10:54] sure [10:54] i'm a little worried about the new user being very confusing by the bug page, particularly the task list, but... [10:55] <\sh> bradb: can u explain again, why the assigned maintainer should be able to edit the original bug description? [10:55] any way to make 2 modes maybe? [10:55] I'd like a page with edit+comments [10:55] for people opening bug or for people working? [10:55] I really like the bugzilla approach [10:55] \sh: to make it more accurate and useful than the first comment that was added to the bug [10:56] seb128: hmm... [10:56] 2 modes sounds a bit complicated (not just to implement, but i mean to use it seems like it might be a bit complicated) [10:57] <\sh> bradb: so, thinking about workflow in a customer care center...the customer is calling in, and giving a problem description. this description is fixed forever. the assigned supporter will have to comment on the problem not to edit the first description of the problem [10:57] seb128: should we just say that landing on the bug page for now is an appropriate and workable solution to #2 for now? [10:57] \sh: that's not how it works in Malone :) [10:58] bradb: yep [10:58] ok, fair enough, noted. #3 then. [10:58] what does #3 mean exactly? [10:58] just a note [10:58] <\sh> bradb: thats right, and this is whats confusing. cause working the whole time with ticketing systems and bugzilla, you are used to the "question" "response" system [10:58] how do I edit the bug description ? [10:58] <\sh> seb128: "edit bug details" [10:58] \sh: and then? [10:58] [16:53] seb128: click on Edit Bug Details from the bug page [10:59] <\sh> dholbach: and then what? ,-) [10:59] ups, sorry, I though it was related to the task/bug page [10:59] ah yes, yes [10:59] not easy to find [10:59] going to the corner list [10:59] \sh: being able to concentrate the current state of the bug is nice too however === dholbach nods [11:00] seb128: the description is something on the bug as a whole (rather than related to fixing the bug in a specific place), so it's a bug page thing, not a task page thing. [11:00] the dbs has some bugs with a _lot_ of comments, you then have to read everything to understand what is going on [11:00] seb128: is #3 something that needs to be noted then or not? if so, i'll need to get more info from you on what the problem there is, specifically as you've worded it in #3. [11:01] <\sh> LarstiQ: but if you edit the first "problem description" you are changing the original data of the reporter. [11:01] bradb: no, that's just the "edit bug" not discovrable on the page [11:02] I've not figured how to go from bug to task [11:02] \sh: the original data of the reporter is also the first comment on the bug :) [11:02] \sh: with edit history, I don't experience that as much of a problem [11:02] seb128: can you show me the url at which point you're lost, and where you're trying to get to when looking at that URL? [11:02] <\sh> bradb: it doesn't show up to me like a comment when I'm on the "bug description and discussion" page [11:03] bradb: how can I assign a bug to me, from the bug page?? [11:03] bradb: k [11:03] \sh: yes it does :) [11:03] <\sh> seb128: when you're on "bug description and discussion" page click on the list with "upstream/package" etc. [11:03] \sh: it's the first comment on the bug, at the bottom of the page. [11:03] bradb: https://launchpad.ubuntu.com/malone/bugs/543 [11:03] bradb: I want to close the bug, where do I click? [11:04] bradb: hum rather, I want the tasks for the bug [11:04] seb128: ok, so keep in mind that a bug can exist in many places [11:04] exactly [11:04] <\sh> bradb: u see, i'm lost...i read the first description as the first entry..then I have the newest comments, and then the original description again as comment... [11:04] so, you want to close it in your neck of the woods [11:04] seb128: but this is /precisely/ what i was saying earlier about my concern with having people land on the bug page :) that they'd be confused by the task listing. [11:05] seb128: but yeah, you just click on your task in the task listing [11:05] <\sh> bradb: change it from a static list with link to a small table with all data and form widgets to change... [11:05] when i try to click on "ubuntu verbiste" from mentioned page, i get a "404" error [11:06] bradb: I'm probably stupid, but I don't find any task on this page? [11:06] ups [11:06] that's the first line [11:06] dholbach: that's a hint to me to make that clicking do what the user expects :) when you click on the row itself (/not/ the underlined link) it'll do what you expect. [11:06] nm [11:06] <\sh> bradb: have a look on "request tracker" how they are handling requests and tasks (http://www.bestpractical.com/rt/) [11:06] seb128: no, it really /is/ that confusing, unfortunately :/ [11:06] I'm too used to bugzilla, I was taking that as the bug summary [11:07] bradb: ok [11:07] bradb: i think the problem is that the bug page and the task page are too decoupled, it might be a good idea to make it easier to change things from the bug page [11:07]