| ../irclogs/#mantishelp.2010-07-13.log | ||
| --- scribe started --- | 00:00 | |
| mantisbt_92029 | hello | 02:02 |
|---|---|---|
| mantisbt_92029 | hi | 02:02 |
| mantisbt_92029 | anyone there? | 02:03 |
| mantisbt_92029 | hi tavasti | 02:04 |
| mantisbt_92029 | a u there? | 02:04 |
| mantisbt_92029 | anyone can help me | 02:05 |
| mantisbt_92029 | i need help from you all | 02:05 |
| nuclear_eclipse | "Just Ask!" | 02:06 |
| mantisbt_92029 | Need to show location in viewing issue list at view_all_bug_page.php. There are only available column "P", "ID", "#", "Category", "Severity", "Status", 'Updated', 'Summary'. Kindly guide how to add column to get location. | 02:06 |
| nuclear_eclipse | Manage -> Manage Configuration -> Manage Columns | 02:07 |
| mantisbt_92029 | in mantis 1.2.0 there are manage column functionality which we can configure to add custom location column in view issue column | 02:08 |
| mantisbt_92029 | but in mantis 1.1.8 doesn't having that functionality to add | 02:08 |
| mantisbt_92029 | any idea | 02:08 |
| nuclear_eclipse | it's not supported in 1.1.8 | 02:09 |
| mantisbt_92029 | is it any idea or solution we can configure it? | 02:09 |
| mantisbt_92029 | at back end | 02:10 |
| mantisbt_92029 | in coding side to show the that location in viewing issue | 02:10 |
| nuclear_eclipse | not that I know of; that code is very complex to deal with | 02:11 |
| mantisbt_92029 | is it? | 02:11 |
| mantisbt_92029 | but do you know which php file holding this configuration | 02:12 |
| mantisbt_92029 | i need to location in bottom in viewing issues area | 02:13 |
| mantisbt_92029 | not in filtering area at top | 02:13 |
| mantisbt_92029 | in view_all_bug_page.php | 02:13 |
| nuclear_eclipse | config_defaults_inc.php might have something you can override of interest, but otherwise, I'm not sure that I can help you | 02:13 |
| mantisbt_92029 | ok sir | 02:14 |
| mantisbt_92029 | thanks for your advice | 02:14 |
| mantisbt_92029 | good day | 02:14 |
| mantisbt_92029 | bye | 02:14 |
| nuclear_eclipse | you're welcome | 02:14 |
| mantisbt_92029 | take care | 02:14 |
| mantisbt_00194 | hi nuclear_eclipse | 02:28 |
| mantisbt_00194 | i just found out the config_default_inc to edit the configuration | 02:29 |
| mantisbt_00194 | it say that | 02:29 |
| mantisbt_00194 | This configuration can be overriden dynamically by overriding the custom function "get_columns_to_view". | 02:29 |
| mantisbt_00194 | can i know which php file they mention | 02:30 |
| mantisbt_00194 | custom function "get_column_to_view" | 02:30 |
| mantisbt_00194 | a u there? | 02:30 |
| mantisbt_00194 | hi nuclear | 02:33 |
| mantisbt_00194 | a u there/ | 02:33 |
| mantisbt_00194 | anyone there? | 02:33 |
| mantisbt_00194 | anyone can help me | 02:36 |
| mantisbt_00194 | plz can anyone help me | 02:38 |
| mantisbt_00194 | hi | 02:39 |
| nuclear_eclipse | http://manual.mantisbt.org/manual.customizing.mantis.custom.functions.example.custom.function.php | 02:40 |
| nuclear_eclipse | http://manual.mantisbt.org/manual.customizing.mantis.custom.functions.php | 02:40 |
| 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. | 04: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? | 04:16 |
| ToffeePops | (Correction - developers and above...) | 04: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";} | 04:16 |
| ToffeePops | How does mantis know that the row 'update_issues_page_columns' even exists and that it should apply that rule? | 04:17 |
| 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? | 08:17 |
| istvanb | hi there! | 08:31 |
| istvanb | If I try to report an issue as a reporter than is there a reason why I can not select the target version? | 08:31 |
| istvanb | if I login as a developer it just works fine | 08:32 |
| istvanb | dmx_h hello | 09:24 |
| istvanb | hello hello | 11:26 |
| istvanb | is there anybody? | 11:27 |
| nuclear_eclipse | istvanb: there is a configurable threshold to determine who can set target versions, roadmap_update_threshold iirc | 11:34 |
| istvanb | great! | 11: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 | 11: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? | 11:38 |
| nuclear_eclipse | if the reporter doesn't have access level to change it, it should hide it automatically | 11:39 |
| istvanb | its true for the target version, but the current version field is visible | 11:45 |
| nuclear_eclipse | ah, that's a separate threshold | 11:48 |
| nuclear_eclipse | there are separate thresholds for just about everything :P | 11:48 |
| istvanb | another question: a reporter creates a new issue, but nobody get a notification about it | 12: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 | 12:48 |
| istvanb | on the manage notifications page all the checkboxes are checked (except the viewer, reporter, updater and admin columns" | 12:49 |
| istvanb | "user who reported the issue" is checked so so whenever i move the issue the reporter should recieve the notification | 12:51 |
| istvanb | ? | 12:51 |
| istvanb | $g_enable_email_notification= ON; | 12:52 |
| istvanb | $g_email_receive_own= ON; | 12:52 |
| istvanb | for the specific project I am added as a developer (I have reporter credentials by default) | 12:54 |
| istvanb | hmm... it looks like something intermittent, because now it works fine | 13:06 |
| 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? | 13:53 |
| nuclear_eclipse | why would you want to disallow access to those pages? | 13:57 |
| nuclear_eclipse | I can't imagine that every user would be happy with the default preferences | 13:58 |
| magnetik | Hi | 14:03 |
| magnetik | Where is the file to modify the footer on every page ? | 14:03 |
| istvanb | well, I just simply dont want them to modifiy all these things | 14:04 |
| istvanb | magnetik: what you mean exactly? | 14:04 |
| nuclear_eclipse | magnetik: that's defined in your configuration | 14:04 |
| istvanb | mantis logo? Webmaster address? | 14:04 |
| magnetik | Humm, I want to add some html content on every page, in the footer | 14:04 |
| nuclear_eclipse | magnetik: you can configure mantis to include an HTML page in the header and/or footer of every page | 14:05 |
| magnetik | Sounds good ; how ? | 14:05 |
| nuclear_eclipse | there's a value in config_defaults_inc.php that you should copy to your config_inc.php and modify there | 14:07 |
| magnetik | ok ; thanks ! | 14:08 |
| istvanb | nuclear_eclipse: is there a document describing how to develop plugins? | 14:08 |
| nuclear_eclipse | http://docs.mantisbt.org/release-1.2.1/en/developers/ | 14:13 |
| nuclear_eclipse | it's incomplete, but is enough to get you started down the right path | 14:13 |
| nuclear_eclipse | there is plenty of example code to look at on http://git.mantisforge.org | 14:14 |
| nuclear_eclipse | source-integration is a good example of a very complex set of plugins | 14:15 |
| nuclear_eclipse | something like announcements is much more straightforward | 14:15 |
| istvanb | thx! | 14:15 |
| nuclear_eclipse | just note that plugins are much more oriented to adding new features to mantis, rather than modifying core behaviors | 14:16 |
| istvanb | as I told before I dont have php knowledge but this may change in the future | 14:16 |
| istvanb | its good to know where to start if I want to develop a plugin | 14:16 |
| istvanb | wont happen in the next couple months though | 14:17 |
| magnetik | nuclear_eclipse, I'm sorry but I've read all lines of config_defaults_inc and I can't find the correct line | 14:26 |
| nuclear_eclipse | $g_bottom_include_page | 14:27 |
| magnetik | Thanks a lot | 14: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 :) | 14:30 |
| nuclear_eclipse | congrats :) | 14: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 | 14:34 |
| istvanb | $s_status_enum_string = '100:Reported, 200:Assigned, 300:In work, 400:In review, 500:Resolved, 900:Closed, 999:Rejected/canceled'; | 14:38 |
| istvanb | and I got a division by zero error message | 14:38 |
| istvanb | maybe its a config issue on my side | 14:41 |
| istvanb | I think i got it | 14:42 |
Generated by irclog2html.py