Monday, 2011-10-17

*** Joins: kirillka (~Miranda@195.242.142.17)00:53
*** Joins: giallu (~giallu@fedora/giallu)01:40
*** Joins: soc42 (~soc42@f051036177.adsl.alicedsl.de)03:14
*** Quits: soc42 (~soc42@f051036177.adsl.alicedsl.de) (Ping timeout: 245 seconds)03:22
*** Joins: dhx1 (~anonymous@60-242-108-164.static.tpgi.com.au)03:59
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 248 seconds)04:07
*** Quits: siebrand (~siebrand@5353A6DC.cm-6-4c.dynamic.ziggo.nl) (Read error: Connection reset by peer)04:32
*** Joins: siebrand (~siebrand@5353A6DC.cm-6-4c.dynamic.ziggo.nl)04:32
*** Joins: giallu (~giallu@fedora/giallu)04:51
*** Quits: siebrand (~siebrand@5353A6DC.cm-6-4c.dynamic.ziggo.nl) (Quit: siebrand)06:30
*** Joins: siebrand (~siebrand@5353A6DC.cm-6-4c.dynamic.ziggo.nl)06:32
*** Quits: siebrand (~siebrand@5353A6DC.cm-6-4c.dynamic.ziggo.nl) (Ping timeout: 255 seconds)06:36
*** Joins: roeni (~Roeni@g226233048.adsl.alicedsl.de)07:29
roeni Is it possible to limit changeability of priority field in bug reports? Reporters shall not be able to change that value but Testers (and higher) shall be able to do that.07:30
*** Quits: dhx1 (~anonymous@60-242-108-164.static.tpgi.com.au) (Remote host closed the connection)08:11
*** Joins: spq (~spq@static-87-79-73-36.netcologne.de)08:32
spqhey there, we are using mantis in a company and have set up much projects with different access levels and such, im searching for a solution to manage the access levels more easily, currently im using direct db access to manage them, i would like to handle the users by using groups or roles or something is this possible? probably with a plugin?09:22
*** Quits: kirillka (~Miranda@195.242.142.17) (Quit: kirillka)09:55
dregadspq: this is a feature that has been requested for a long time, unfortunately Mantis does not allow it for now10:30
dregadhttp://www.mantisbt.org/bugs/view.php?id=344410:30
spq:(10:30
spqthanks10:31
*** Joins: yareckon (~yareckon@p5DDBB937.dip.t-dialin.net)11:07
yareckonhi guys, we have a mantis install that covers about 30 projects... There are many developers and project managers that are admins in the system, but I'd like to set one "Project owner" per project who gets notified for new tickets.  Is there a configuration option anywhere to do this, or another way to solve my problem?11:09
*** Quits: roeni (~Roeni@g226233048.adsl.alicedsl.de) (Quit: Verlassend)12:27
dregadyareckon: e-mail notifications can be set to send by access level12:32
dregadbut it's not possible by specific user12:32
dregadand the user can override this with their personal preferences12:32
dregadmanage / configurations / e-mail notifications, then check "manager" for "status changes to new"12:33
yareckonif I am a global admin, can I be a "manager" for this project?12:36
yareckonthe problem is likely that we simply have too flat of a structure with too many folks set to "admin"12:37
yareckonand I can't be both an admin in mantis and a manager for a specific project as far as I can see12:40
dregadyareckon: something you could try12:46
dregaddisclaimer: I have not tested this, and I think it would be quite time-consuming to setup and hard to maintain12:46
yareckongo on :)12:46
dregadthe e-mail notification can be overridden, just like any other config in mantis12:47
dregadso if you go in the manage configuration view, you can then set user-specific notification12:47
dregadsay, for user XXX, notify_flags12:48
dregadthe syntax of the array is a bit complex12:48
dregadso set it first in the GUI for a project, then copy the config for the specific user12:48
yareckonok12:48
dregadI think it would work, but as i said, it would be a b*tch to maintain12:49
yareckonyeah, or we could just train everyone to assign every bug to some hapless soul for each project12:49
yareckonis there auto assign or default assign?  That would be just as good12:50
dregadauto assignment can be done based on categories12:50
yareckonsounds like I have some docs to read12:51
dregadglobally, and by project12:51
yareckongreat, that sounds like it would be the way to go12:51
dregadgg, good luck12:51
yareckonthanks for talking this through with me12:52
yareckonand for the software :)12:52
*** Joins: siebrand (~siebrand@cable-48-77.zeelandnet.nl)12:53
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 248 seconds)14:03
*** Joins: giallu (~giallu@fedora/giallu)14:05
*** Quits: siebrand (~siebrand@cable-48-77.zeelandnet.nl) (Quit: siebrand)14:57
*** Joins: siebrand (~siebrand@cable-64-212.zeelandnet.nl)16:22
*** Quits: siebrand (~siebrand@cable-64-212.zeelandnet.nl) (Ping timeout: 276 seconds)16:57
*** Quits: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com) (Read error: Connection refused)19:19
*** Joins: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com)19:37
*** Quits: yareckon (~yareckon@p5DDBB937.dip.t-dialin.net) (Quit: yareckon)19:53
*** Quits: sdfjkljkdfsljkl (~sdfjkljkd@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)20:00
*** Joins: sdfjkljkdfsljkl (~sdfjkljkd@static.96.23.63.178.clients.your-server.de)20:00
*** Quits: saparvia (~quassel@flkl-void.acclab.helsinki.fi) (*.net *.split)20:51
*** Quits: spq (~spq@static-87-79-73-36.netcologne.de) (*.net *.split)20:51
*** Joins: spq (~spq@static-87-79-73-36.netcologne.de)20:55
*** Joins: saparvia (~quassel@flkl-void.acclab.helsinki.fi)20:55
*** Quits: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com) (Read error: Connection refused)21:49
*** Joins: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com)22:02
*** Quits: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com) (Read error: Connection refused)22:10
*** Joins: micahg (~micahg@24-148-38-99.c3-0.arm-ubr3.chi-arm.il.cable.rcn.com)22:27

Generated by irclog2html.py 2.10.0 by Marius Gedminas - find it at mg.pov.lt!