*** Joins: siebrand (~beis@sm.xs4all.nl) | 00:58 | |
*** Quits: siebrand_alt (~beis@sm.xs4all.nl) (Ping timeout: 260 seconds) | 00:59 | |
*** Joins: kirillka (~Miranda@global01.vester.ru) | 01:15 | |
*** Quits: siebrand (~beis@sm.xs4all.nl) () | 01:35 | |
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds) | 02:06 | |
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 02:31 | |
*** Joins: giallu (~giallu@fedora/giallu) | 02:33 | |
*** Joins: mantisbt_05140 (~72ff2c84@gateway/web/freenode/x-fzvpiszkonrydrsf) | 03:32 | |
*** Quits: mantisbt_05140 (~72ff2c84@gateway/web/freenode/x-fzvpiszkonrydrsf) (Client Quit) | 03:32 | |
*** Joins: davidinc (~d5374b0d@gateway/web/freenode/x-cuzyzhsjtiwexnze) | 03:45 | |
*** Quits: micahg1 (~micah@24-148-9-11.arm-bsr1.chi-arm.il.cable.rcn.com) (Ping timeout: 240 seconds) | 03:54 | |
*** Joins: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) | 04:37 | |
*** Quits: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) (Read error: Connection reset by peer) | 04:41 | |
*** Joins: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) | 04:45 | |
*** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) | 05:54 | |
*** Quits: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) (Read error: Operation timed out) | 05:57 | |
*** Joins: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) | 06:10 | |
*** Quits: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) (Ping timeout: 248 seconds) | 06:25 | |
*** Joins: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) | 06:38 | |
*** Quits: rolfkleef (~rolf@82-204-30-154.dsl.bbeyond.nl) (Ping timeout: 276 seconds) | 07:09 | |
*** Joins: rolfkleef (~rolf@a82-95-123-174.adsl.xs4all.nl) | 07:49 | |
*** Joins: AzaToth (~azatoth@wikipedia/AzaToth) | 08:14 | |
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 09:16 | |
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 09:18 | |
*** Quits: mophilly (~mophilly@mail.mophilly.com) (Quit: mophilly) | 09:32 | |
*** Quits: rolfkleef (~rolf@a82-95-123-174.adsl.xs4all.nl) (Ping timeout: 264 seconds) | 09:40 | |
*** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) | 10:23 | |
*** Joins: fanno (~Morten@90.184.93.233) | 10:57 | |
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 11:06 | |
*** Parts: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) | 11:13 | |
daryn | nuclear_eclipse there? | 11:17 |
---|---|---|
*** Joins: micahg (~micah@ubuntu/member/micahg) | 11:50 | |
nuclear_eclipse | hi daryn | 12:13 |
daryn | hello | 12:14 |
daryn | working on filter by date | 12:14 |
daryn | looking for some input | 12:14 |
nuclear_eclipse | ok | 12:15 |
nuclear_eclipse | opinion: current filter by date sucks balls | 12:15 |
daryn | one of the requests in the bug tracker is to be able to filter by the issues resolved in the last x days or status changed in date range, etc. | 12:15 |
daryn | i have a start and end date jquery calendar working | 12:15 |
daryn | well...partially working | 12:15 |
nuclear_eclipse | daryn: a) please drop the need to tick a checkbox just to be able to filter on a date... | 12:16 |
daryn | done already | 12:16 |
daryn | :) | 12:16 |
nuclear_eclipse | yay! | 12:16 |
daryn | it was so dumb | 12:16 |
daryn | if there are dates filter by them...if not don't! | 12:17 |
daryn | how hard is that | 12:17 |
nuclear_eclipse | I think filtering on any history entries in a date range would be acceptable, IMO | 12:17 |
daryn | anyway... | 12:17 |
daryn | k. so selecting which is the issue | 12:17 |
daryn | i'm thinking ... | 12:17 |
daryn | checkboxes next to date fields for resolved, status change, etc. | 12:17 |
daryn | date submitted, last updated | 12:18 |
nuclear_eclipse | well, my point is that I think it's going to be almost impossible to be comprehensive on what history entries to look for, so just ignore the history entry's type | 12:18 |
daryn | hm... | 12:18 |
nuclear_eclipse | ie, have a way to search for issues with *any change* inside that date range | 12:18 |
nuclear_eclipse | if you want issues resolved inside that date range, just combine the standard status filter with the history entry filter | 12:18 |
daryn | well...resolved and status are specified fields and are likely to be searched frequently i think | 12:18 |
daryn | that's what i was thinking... | 12:19 |
daryn | except that i think we need to check the changed value in the history | 12:19 |
*** Joins: sirscott (~scott@c-71-229-182-62.hsd1.co.comcast.net) | 12:19 | |
daryn | as it's possible that the current status is not the same as what they want in the date range | 12:19 |
nuclear_eclipse | well, my point is that if you add a specific filter to find only status changes within the history entry range, then people are going to complain that you can't do the same for every other history entry type, esp for types created by plugins | 12:19 |
sirscott | just installed mantis 1.2.1 --> created the administrator account and then logged in to create a new admin user as instructed. How can I set the new admin account password? | 12:20 |
daryn | yeah...could get a bit crazy | 12:20 |
nuclear_eclipse | sirscott: go to My Account while logged in as the admin account | 12:20 |
sirscott | yup, did that, created an account, but there's no place to insert a password? | 12:21 |
sirscott | oops, I went to 'manage --> manage users" | 12:21 |
sirscott | and then created a new admin account | 12:21 |
daryn | nuclear_eclipse i'm torn on the status/resolved history thing... i'll think about it some more | 12:22 |
nuclear_eclipse | sirscott: afaik, mantis doesn't allow an admin to set another user's password, only to force a password reset so the user can change their password | 12:22 |
sirscott | nuclear_eclipse: the instructions state to remove the account 'adminstrator' so i don't see what help changing its password there is | 12:22 |
sirscott | nuclear_eclipse: ah crap, and the password reset is only with email, no? i don't have a working email setup | 12:22 |
daryn | sirscott you can just rename the administrator user and reset the password to blank | 12:23 |
nuclear_eclipse | yes, the password reset requires email, but if you can log in as the user account, you can can change the password that way | 12:23 |
daryn | nuclear_eclipse regarding dates... custom field date has selection list... | 12:23 |
sirscott | ok, so what's the default user password when I create the account? | 12:23 |
daryn | on, on or after, on or before, between, none, etc | 12:24 |
nuclear_eclipse | sirscott: if you create an account, it doesn't have a password yet | 12:24 |
daryn | nuclear_eclipse: i'm thinking of dropping the selection with the following logic | 12:24 |
sirscott | nuclear_eclipse: ah maybe i need to disable ($g_enable_email_notification) so that the account gets created with a blank password | 12:25 |
daryn | nuclear_eclipse: on or before - only set the end date, on or after - only set the start date, between-duh, on - maybe set both to same date?, before and after are unnecessary, none - checkbox maybe | 12:25 |
nuclear_eclipse | daryn: just do whatever ends up with the simplest UI | 12:28 |
nuclear_eclipse | that's what I'm always trying to strive for with any change I make | 12:28 |
daryn | right, me too. i'm just not sure what i think is simple always translates to simple for others | 12:28 |
daryn | so, do you think the above would be too confusing? should we keep the dropdown and add it to standard date filter? | 12:29 |
nuclear_eclipse | daryn: I'd like to see the custom field thing just look exactly like the normal date filter, ie, two inclusive date selections, and just be done with it | 12:29 |
sirscott | why is 'user@localhost' considered an invalid e-mail address when 'root@localhost' for the autocreated adminstrator account is fine? | 12:32 |
daryn | nuclear_eclipse: ok. thx | 12:32 |
davidinc | daryn: First on the string it doesn't tell you the filter method for example change Use Date Filters to Use Date Filters By Reported Date: like that. | 12:34 |
daryn | davidinc: that's a simple enough change | 12:35 |
davidinc | daryn: I know | 12:35 |
daryn | davidinc: what about filtering for other dates though? | 12:35 |
davidinc | daryn: exactly | 12:35 |
davidinc | you can't filter the issues you modified or updated recently becausse the filter use the reported stamp. | 12:36 |
daryn | davidinc: nuclear_eclipse: should we just add a completely different date search for others, ie history? or a selection for which to search? | 12:36 |
daryn | davidinc: right | 12:36 |
daryn | due date is another that would likely be searched frequently | 12:37 |
*** Joins: moto-moi (~hylke@cara.xs4all.nl) | 12:37 | |
davidinc | exactly | 12:37 |
davidinc | I were wrighting that | 12:37 |
davidinc | writting that | 12:37 |
daryn | i've got a major overhaul to filters hopefully coming soon...working out kinks right now | 12:38 |
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 260 seconds) | 12:38 | |
daryn | filter api is essentially gone ( there but deprecated and unused ) | 12:38 |
davidinc | some how we shell make the filter function much better!!!! | 12:39 |
nuclear_eclipse | sirscott: good question, post a bug on the tracker, and I'll see what I can do about it | 12:40 |
daryn | so...i'm thinking due date, date submitted, history dates, etc. should be separate fields | 12:40 |
daryn | the ui would be more obvious and would allow multiple date filters | 12:41 |
nuclear_eclipse | daryn: could always just share a UI mockup before you actually write the backend code for it, and get some feedback that way | 12:42 |
davidinc | daryn: I agree with you!! | 12:44 |
daryn | nuclear_eclipse: could...but i want to write it now. :) | 12:46 |
nuclear_eclipse | hehe | 12:48 |
nuclear_eclipse | no worries | 12:48 |
daryn | nuclear_eclipse: between you, davidinc, and a co-worker i think i've got enough input for now. thanks guys | 12:49 |
nuclear_eclipse | np | 12:55 |
nuclear_eclipse | now get to work, slacker :P | 12:55 |
daryn | oh, don't even get me started! :P | 12:56 |
sirscott | nuclear_eclipse: will do, thanks for your help :) | 13:19 |
*** Quits: davidinc (~d5374b0d@gateway/web/freenode/x-cuzyzhsjtiwexnze) (Ping timeout: 252 seconds) | 13:35 | |
*** Joins: micahg (~micah@ubuntu/member/micahg) | 13:58 | |
*** Joins: siebrand (~beis@sm.xs4all.nl) | 14:32 | |
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 248 seconds) | 14:49 | |
*** Joins: micahg (~micah@ubuntu/member/micahg) | 14:51 | |
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds) | 15:03 | |
*** Quits: fanno (~Morten@90.184.93.233) (Ping timeout: 240 seconds) | 15:18 | |
*** Joins: micahg (~micah@ubuntu/member/micahg) | 15:20 | |
*** Joins: fanno (~Morten@90.184.93.233) | 15:20 | |
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds) | 15:25 | |
*** Joins: micahg (~micah@ubuntu/member/micahg) | 15:58 | |
*** Quits: fanno (~Morten@90.184.93.233) (Quit: Leaving.) | 16:52 | |
*** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat) | 17:32 | |
*** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Quit: Ex-Chat) | 18:01 | |
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds) | 19:40 | |
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection) | 19:59 | |
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) | 20:00 | |
*** Quits: AzaToth (~azatoth@wikipedia/AzaToth) (Remote host closed the connection) | 20:12 | |
*** Joins: FFForever (~Chris@unaffiliated/ffforever) | 20:30 | |
FFForever | Good Evening | 20:30 |
*** Joins: siebrand_alt (~beis@sm.xs4all.nl) | 20:58 | |
*** Quits: siebrand (~beis@sm.xs4all.nl) (Ping timeout: 240 seconds) | 20:59 | |
*** Quits: siebrand_alt (~beis@sm.xs4all.nl) (Ping timeout: 240 seconds) | 21:14 | |
*** Joins: siebrand (~beis@sm.xs4all.nl) | 21:14 | |
*** Joins: micahg (~micah@ubuntu/member/micahg) | 22:05 | |
*** Quits: sirscott (~scott@c-71-229-182-62.hsd1.co.comcast.net) (*.net *.split) | 22:25 | |
*** Joins: |HaruAFK| (~haruka@p54ACFB4A.dip.t-dialin.net) | 22:25 | |
*** Joins: sirscott (~scott@c-71-229-182-62.hsd1.co.comcast.net) | 22:28 | |
*** Quits: |Otter| (~haruka@p54ACFD49.dip.t-dialin.net) (Ping timeout: 264 seconds) | 22:29 | |
*** Quits: kirillka (~Miranda@global01.vester.ru) (Quit: kirillka) | 23:56 |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!