| *** Joins: ToffeePops (~chatzilla@202.20.3.13) | 00:04 | |
| ToffeePops | nuclear_eclipse: Hi, you helped me to disable editing of 'additional info' by setting $g_bug_update_page_fields in the config_inc.php file. | 00:16 |
|---|---|---|
| ToffeePops | But I wanted to allow editing for managers... so I added 'update_issues_page_columns' to the mantis_config_table, which what I hoped would be the correct setting. Are you able to see if this is right? | 00:16 |
| ToffeePops | (Correction - developers and above...) | 00:16 |
| ToffeePops | a:14:{i:0;s:9:"selection";i:1;s:4:"edit";i:2;s:8:"priority";i:3;s:2:"id";i:4;s:17:"sponsorship_total";i:5;s:14:"bugnotes_count";i:6;s:11:"category_id";i:7;s:8:"severity";i:8;s:6:"status";i:9;s:12:"last_updated";i:10;s:7:"summary";i:11;s:11:"description";i:12;s:15:"additional_info";i:13;s:18:"steps_to_reproduce";} | 00:16 |
| ToffeePops | How does mantis know that the row 'update_issues_page_columns' even exists and that it should apply that rule? | 00:17 |
| *** Joins: fanno (~b3g@193.3.95.240) | 00:24 | |
| *** Quits: fanno (~b3g@193.3.95.240) (Read error: Connection reset by peer) | 01:02 | |
| *** Joins: kirillka (~Miranda@global01.vester.ru) | 01:09 | |
| *** Joins: fanno (~b3g@193.3.95.240) | 01:57 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 02:33 | |
| *** Quits: fanno (~b3g@193.3.95.240) (Read error: Connection reset by peer) | 02:49 | |
| *** Quits: siebrand_alt (~beis@sm.xs4all.nl) () | 02:55 | |
| *** Joins: fanno (~b3g@193.3.95.240) | 02:59 | |
| *** Joins: giallu (~giallu@fedora/giallu) | 03:04 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 248 seconds) | 03:11 | |
| *** Joins: AlienPenguin (~my@79.171.63.250) | 04:15 | |
| AlienPenguin | hi all, i want to migrate mantis 1.1.6 to 1.2.1 but on another pc, should i first install the 1.2.1 and then restore the db (mysql, is the db format unchanged between 1.1.6 and 1.2.1?) or should i create a fake db, import the data and then install 1.2.1? | 04:17 |
| *** Joins: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) | 04:30 | |
| istvanb | hi there! | 04:30 |
| istvanb | If I try to report an issue as a reporter than is there a reason why I can not select the target version? | 04:31 |
| istvanb | if I login as a developer it just works fine | 04:31 |
| istvanb | dmx_h hello | 05:24 |
| *** Joins: moto-moi (~hylke@cara.xs4all.nl) | 05:33 | |
| *** Quits: ToffeePops (~chatzilla@202.20.3.13) (Ping timeout: 248 seconds) | 05:49 | |
| *** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 265 seconds) | 07:24 | |
| istvanb | hello hello | 07:26 |
| istvanb | is there anybody? | 07:26 |
| nuclear_eclipse | istvanb: there is a configurable threshold to determine who can set target versions, roadmap_update_threshold iirc | 07:34 |
| istvanb | great! | 07:36 |
| istvanb | I assume that the reporters will always report bugs of the current version, so it makes sense that only developers can set this version | 07:36 |
| istvanb | for this it makes no sense to make the version field visible for the reporters. Is there a way to hide this field from reporters but make it visible if a developer or so report the issue? | 07:37 |
| nuclear_eclipse | if the reporter doesn't have access level to change it, it should hide it automatically | 07:39 |
| *** Quits: fanno (~b3g@193.3.95.240) (Read error: Connection reset by peer) | 07:44 | |
| istvanb | its true for the target version, but the current version field is visible | 07:45 |
| nuclear_eclipse | ah, that's a separate threshold | 07:48 |
| nuclear_eclipse | there are separate thresholds for just about everything :P | 07:48 |
| *** Quits: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) (Ping timeout: 252 seconds) | 08:16 | |
| *** Joins: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) | 08:19 | |
| *** Joins: fanno (~Morten@90.184.93.233) | 08:43 | |
| istvanb | another question: a reporter creates a new issue, but nobody get a notification about it | 08:47 |
| istvanb | when I pick up the issue and move to the next phase then I as a developer recieves a mail, but not the reporter | 08:48 |
| istvanb | on the manage notifications page all the checkboxes are checked (except the viewer, reporter, updater and admin columns" | 08:49 |
| istvanb | "user who reported the issue" is checked so so whenever i move the issue the reporter should recieve the notification | 08:51 |
| istvanb | ? | 08:51 |
| istvanb | $g_enable_email_notification= ON; | 08:52 |
| istvanb | $g_email_receive_own= ON; | 08:52 |
| istvanb | for the specific project I am added as a developer (I have reporter credentials by default) | 08:54 |
| *** Joins: giallu (~giallu@fedora/giallu) | 08:58 | |
| istvanb | hmm... it looks like something intermittent, because now it works fine | 09:06 |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 09:44 | |
| istvanb | nuclear_eclipse: I dont want the users to access to the Manage columns and the Preferences windows. I can make the user protected, but then they can not change the password? Any solution for that? | 09:53 |
| nuclear_eclipse | why would you want to disallow access to those pages? | 09:57 |
| nuclear_eclipse | I can't imagine that every user would be happy with the default preferences | 09:57 |
| *** Quits: kirillka (~Miranda@global01.vester.ru) (Quit: kirillka) | 10:02 | |
| *** Joins: magnetik (~magnetik@blacksburg.torctech.com) | 10:02 | |
| magnetik | Hi | 10:02 |
| magnetik | Where is the file to modify the footer on every page ? | 10:03 |
| istvanb | well, I just simply dont want them to modifiy all these things | 10:04 |
| istvanb | magnetik: what you mean exactly? | 10:04 |
| nuclear_eclipse | magnetik: that's defined in your configuration | 10:04 |
| istvanb | mantis logo? Webmaster address? | 10:04 |
| magnetik | Humm, I want to add some html content on every page, in the footer | 10:04 |
| nuclear_eclipse | magnetik: you can configure mantis to include an HTML page in the header and/or footer of every page | 10:05 |
| magnetik | Sounds good ; how ? | 10:05 |
| nuclear_eclipse | there's a value in config_defaults_inc.php that you should copy to your config_inc.php and modify there | 10:06 |
| magnetik | ok ; thanks ! | 10:07 |
| istvanb | nuclear_eclipse: is there a document describing how to develop plugins? | 10:08 |
| nuclear_eclipse | http://docs.mantisbt.org/release-1.2.1/en/developers/ | 10:12 |
| nuclear_eclipse | it's incomplete, but is enough to get you started down the right path | 10:13 |
| nuclear_eclipse | there is plenty of example code to look at on http://git.mantisforge.org | 10:14 |
| nuclear_eclipse | source-integration is a good example of a very complex set of plugins | 10:14 |
| nuclear_eclipse | something like announcements is much more straightforward | 10:15 |
| istvanb | thx! | 10:15 |
| nuclear_eclipse | just note that plugins are much more oriented to adding new features to mantis, rather than modifying core behaviors | 10:15 |
| istvanb | as I told before I dont have php knowledge but this may change in the future | 10:16 |
| istvanb | its good to know where to start if I want to develop a plugin | 10:16 |
| istvanb | wont happen in the next couple months though | 10:16 |
| *** Joins: mantisbt_18799 (614d61fa@gateway/web/freenode/ip.97.77.97.250) | 10:24 | |
| *** Quits: mantisbt_18799 (614d61fa@gateway/web/freenode/ip.97.77.97.250) (Client Quit) | 10:24 | |
| magnetik | nuclear_eclipse, I'm sorry but I've read all lines of config_defaults_inc and I can't find the correct line | 10:25 |
| nuclear_eclipse | $g_bottom_include_page | 10:27 |
| magnetik | Thanks a lot | 10:27 |
| istvanb | nuclear_eclipse: hey but I have a good news. Yesterday I made a short presentation of Mantis for my managers and they were really impressed. So now we just have to push IT hard to allow us an evaluation :) | 10:30 |
| nuclear_eclipse | congrats :) | 10:30 |
| istvanb | we'll see, they are resistant to any changes but now as I have two managers on my side, I am pretty confident that it's gonna happen | 10:34 |
| istvanb | $s_status_enum_string = '100:Reported, 200:Assigned, 300:In work, 400:In review, 500:Resolved, 900:Closed, 999:Rejected/canceled'; | 10:37 |
| istvanb | and I got a division by zero error message | 10:38 |
| istvanb | maybe its a config issue on my side | 10:40 |
| istvanb | I think i got it | 10:42 |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 10:59 | |
| *** Joins: bigbluehat (~byoung@adsl-177-98-239.gsp.bellsouth.net) | 11:23 | |
| *** Quits: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) (Quit: Page closed) | 11:33 | |
| *** Quits: chris38` (~chris38@bayle.eu) (Ping timeout: 260 seconds) | 11:43 | |
| *** Joins: chris38` (~chris38@bayle.eu) | 11:43 | |
| *** Quits: bigbluehat (~byoung@adsl-177-98-239.gsp.bellsouth.net) (Quit: bigbluehat) | 12:00 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 265 seconds) | 12:08 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 12:12 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 276 seconds) | 12:42 | |
| *** Quits: magnetik (~magnetik@blacksburg.torctech.com) (Quit: Quitte) | 13:03 | |
| *** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer) | 13:04 | |
| *** Quits: moto-moi (~hylke@cara.xs4all.nl) (*.net *.split) | 13:11 | |
| *** Joins: moto-moi (~hylke@cara.xs4all.nl) | 13:13 | |
| *** Joins: bigbluehat (~byoung@68-119-229-144.dhcp.ahvl.nc.charter.com) | 13:41 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 13:49 | |
| *** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 258 seconds) | 14:10 | |
| *** Joins: giallu (~giallu@fedora/giallu) | 14:58 | |
| *** Joins: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) | 15:28 | |
| *** Joins: ToffeePops (~chatzilla@202.20.3.13) | 16:47 | |
| *** Joins: fanno (~Morten@90.184.93.233) | 16:52 | |
| *** Quits: bigbluehat (~byoung@68-119-229-144.dhcp.ahvl.nc.charter.com) (Quit: bigbluehat) | 16:52 | |
| *** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat) | 17:31 | |
| *** Joins: rolfkleef (~rolf@urtica.xs4all.nl) | 17:38 | |
| *** Quits: AlienPenguin (~my@79.171.63.250) (Ping timeout: 240 seconds) | 18:01 | |
| *** Quits: fanno (~Morten@90.184.93.233) (Ping timeout: 264 seconds) | 18:02 | |
| *** Joins: fanno (~Morten@90.184.93.233) | 18:03 | |
| *** Joins: AlienPenguin (~my@79.171.63.250) | 18:14 | |
| *** Quits: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) () | 18:21 | |
| *** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 276 seconds) | 18:47 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 258 seconds) | 19:51 | |
| *** 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 | |
| *** Joins: bigbluehat (~byoung@adsl-177-98-239.gsp.bellsouth.net) | 21:13 | |
| *** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer) | 21:23 | |
| *** Joins: |HaruAFK| (~haruka@p54ACDCAF.dip.t-dialin.net) | 22:18 | |
| *** Quits: |Otter| (~haruka@p54ACC6F7.dip.t-dialin.net) (Ping timeout: 248 seconds) | 22:21 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 22:45 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 246 seconds) | 23:40 | |
| *** Quits: bigbluehat (~byoung@adsl-177-98-239.gsp.bellsouth.net) (Quit: bigbluehat) | 23:40 | |
| *** Joins: micahg (~micah@24-148-9-11.arm-bsr1.chi-arm.il.cable.rcn.com) | 23:43 | |
| *** Quits: micahg (~micah@24-148-9-11.arm-bsr1.chi-arm.il.cable.rcn.com) (Changing host) | 23:44 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 23:44 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!