| chat.freenode.net #tryton log beginning Sun Aug 15 00:00:02 CEST 2010 | ||
| 2010-08-15 00:00 <cedk> sharoon: for priority, I think it is like the invoicing of timesheet etc. | ||
| 2010-08-15 00:01 <cedk> it is so linked to the business rule of a company that it is simplier to create specific modules that handle it | ||
| 2010-08-15 00:01 <cedk> of course these modules could be generic enough to enter in Tryton base | ||
| 2010-08-15 00:02 <cedk> and we should have some because it is some time stopper for some people when you must say that you will develop for them even if it is a few line of code | ||
| 2010-08-15 00:02 <sharoon> cedk: i think the base should be the project revenue? | ||
| 2010-08-15 00:02 <sharoon> cedk: exactly the same functionality will anyhow apply right? | ||
| 2010-08-15 00:04 <sharoon> cedk: also since tickets will now be inheriting on project.work i think thats sufficient to take care of cost/revenue etc?? | ||
| 2010-08-15 00:04 <cedk> sharoon: yes I was talking about priority and I made a comparaison | ||
| 2010-08-15 00:04 <sharoon> cedk: ok | ||
| 2010-08-15 00:05 <cedk> sharoon: but you are right if you talk about a way to invoice tickets | ||
| 2010-08-15 00:05 <sharoon> cedk: alright, so can we finalise on a model for tickets ? | ||
| 2010-08-15 00:05 <cedk> sharoon: but I think the most common way is that you have a prepaid amount of ticket/time and then you just need to check about overflow | ||
| 2010-08-15 00:05 <cedk> sharoon: yes | ||
| 2010-08-15 00:06 <sharoon> cedk: yes, but that could be separate right? | ||
| 2010-08-15 00:06 <sharoon> separate module | ||
| 2010-08-15 00:07 <sharoon> cedk: crazy question: can we have tickets and sub tickets? or in other words, superseder? | ||
| 2010-08-15 00:08 <cedk> sharoon: yes why not and even it is already in timesheet.work | ||
| 2010-08-15 00:08 <sharoon> cedk: in project.work right? | ||
| 2010-08-15 00:08 <cedk> sharoon: no in timesheet.work | ||
| 2010-08-15 00:09 <cedk> but as project.work inherits timesheet.work ... | ||
| 2010-08-15 00:09 <sharoon> cedk: got it http://hg.tryton.org/hgwebdir.cgi/modules/timesheet/file/b3049d956750/work.py#l16 | ||
| 2010-08-15 00:10 <sharoon> ACTION summing up | ||
| 2010-08-15 00:10 <cedk> sharoon: other things, we need to have followers | ||
| 2010-08-15 00:11 <sharoon> cedk: subscribers/folowers | ||
| 2010-08-15 00:11 <sharoon> cedk: followers should be employees / users / or just email iD? | ||
| 2010-08-15 00:13 <cedk> sharoon: why not party? | ||
| 2010-08-15 00:13 <sharoon> got it, all covered | ||
| 2010-08-15 00:13 <sharoon> m2m to party | ||
| 2010-08-15 00:13 <cedk> sharoon: but wait, it is perhaps not for the base module | ||
| 2010-08-15 00:14 <cedk> what is the usage of folowers? | ||
| 2010-08-15 00:14 <sharoon> cedk: people who want to be alerted/keep watch of a specific issue | ||
| 2010-08-15 00:14 <cedk> I think it is only receiving changes | ||
| 2010-08-15 00:14 <cedk> sharoon: so it should go on the module that will make notification | ||
| 2010-08-15 00:15 <sharoon> cedk: ok, somehow notification could be a general module for all objects ? | ||
| 2010-08-15 00:16 <sharoon> cedk: like django-notifications (will work more like a request system for parties (current request is within users)) so you could add someone on a watch for a reference | ||
| 2010-08-15 00:16 <sharoon> cedk: eg: watchers for sale order x | ||
| 2010-08-15 00:16 <sharoon> cedk: and they get alerts whenever the object changes? do you think it can be a generic module? | ||
| 2010-08-15 00:17 <sharoon> cedk: with the use of ir.trigger? | ||
| 2010-08-15 00:18 <cedk> sharoon: I don't know because you must create a template for the change message | ||
| 2010-08-15 00:18 <cedk> sharoon: I think that it requires very few code to write to enable such feature on a business model | ||
| 2010-08-15 00:19 <cedk> because all the work will be done by ir.trigger | ||
| 2010-08-15 00:19 <sharoon> cedk: that could be a generic API? | ||
| 2010-08-15 00:20 <cedk> sharoon: it is already a genenric API -> ir.trigger | ||
| 2010-08-15 00:20 <sharoon> cedk: i am talking about the message | ||
| 2010-08-15 00:21 <cedk> sharoon: don't know | ||
| 2010-08-15 00:21 <cedk> sharoon: at first though I don't see how | ||
| 2010-08-15 00:21 <sharoon> cedk: anyway thats a separate topic | ||
| 2010-08-15 00:21 <sharoon> cedk: it could probably be done by some simple python templating on ir.trigger and email module combination | ||
| 2010-08-15 00:22 <cedk> sharoon: no need of email module :-) Tryton can send emails | ||
| 2010-08-15 00:22 <sharoon> cedk: wov! yes i often forget that | ||
| 2010-08-15 00:24 <sharoon> ok, summing up design | ||
| 2010-08-15 00:28 <sharoon> = Support Ticket System = | ||
| 2010-08-15 00:28 <sharoon> The support ticket works closest to the project / timesheet concepts of Tryton. The objects are | ||
| 2010-08-15 00:28 <sharoon> == Ticket == | ||
| 2010-08-15 00:29 <sharoon> Historised | ||
| 2010-08-15 00:29 <sharoon> _inherits = {'timesheet.work': 'work'} | ||
| 2010-08-15 00:29 <sharoon> * work = Many2One - timesheet.work | ||
| 2010-08-15 00:29 <sharoon> * title = Char | ||
| 2010-08-15 00:29 <sharoon> * description = Char | ||
| 2010-08-15 00:29 <sharoon> * party(fix name if owner) = Many2One - party.party | ||
| 2010-08-15 00:29 <sharoon> * comment = fields.Function(getter-set empty, setter-set the field) | ||
| 2010-08-15 00:29 <sharoon> * assigned_to: Many2One Employee | ||
| 2010-08-15 00:29 <sharoon> * follow_ups: One2Many History | ||
| 2010-08-15 00:30 <sharoon> * status: Many2One ticket.status | ||
| 2010-08-15 00:30 <sharoon> == Status Codes == | ||
| 2010-08-15 00:30 <sharoon> _name = "ticket.status" | ||
| 2010-08-15 00:30 <sharoon> _order = sort_order, ASC | ||
| 2010-08-15 00:30 <sharoon> * name: Char | ||
| 2010-08-15 00:30 <sharoon> * sort_order: Integer | ||
| 2010-08-15 00:31 <sharoon> cedk: does the design look ok? should we maintain a ticket number? random/linear sequence | ||
| 2010-08-15 00:32 <cedk> sharoon: title must be the name of timesheet.work | ||
| 2010-08-15 00:32 <cedk> sharoon: description must be text | ||
| 2010-08-15 00:32 <sharoon> ok | ||
| 2010-08-15 00:32 <cedk> sharoon: merge description and comment | ||
| 2010-08-15 00:33 <cedk> sharoon: state instead of status (like in other modules) | ||
| 2010-08-15 00:33 <cedk> sharoon: sort_order -> sequence | ||
| 2010-08-15 00:34 <sharoon> cedk: reg description i think we will require a description in addition to the comments | ||
| 2010-08-15 00:34 <sharoon> which are follow up | ||
| 2010-08-15 00:34 <cedk> sharoon: I don't think | ||
| 2010-08-15 00:34 <cedk> sharoon: look at roundup | ||
| 2010-08-15 00:34 <sharoon> so it will be more roundup than lp | ||
| 2010-08-15 00:35 <sharoon> cedk: yeh, same thing | ||
| 2010-08-15 00:35 <cedk> sharoon: I don't think it is good to modify the description because it make the convertion more difficult to follow | ||
| 2010-08-15 00:35 <sharoon> cedk: agree | ||
| 2010-08-15 00:35 <cedk> sharoon: I come back to title = timesheet.work name | ||
| 2010-08-15 00:36 <sharoon> cedk: and the design is better | ||
| 2010-08-15 00:36 <cedk> sharoon: infact, I think it is good to have title (char) on ticket | ||
| 2010-08-15 00:36 <cedk> sharoon: we will put sequence number in timesheet.work name | ||
| 2010-08-15 00:37 <sharoon> cedk: so tht will be the ticket number | ||
| 2010-08-15 00:37 <cedk> like that employee when he will fill his timesheet, he will say work on issue1234 | ||
| 2010-08-15 00:37 <sharoon> cool | ||
| 2010-08-15 00:37 <cedk> it is easier than looking to description | ||
| 2010-08-15 00:37 <sharoon> cedk: agree | ||
| 2010-08-15 00:38 <cedk> sharoon: and so ir.sequence defined on config singleton | ||
| 2010-08-15 00:38 <sharoon> cedk: any updates on random sequence generation?\ | ||
| 2010-08-15 00:38 <cedk> sharoon: you mean timestamp | ||
| 2010-08-15 00:38 <cedk> sharoon: I had forgotten :-) | ||
| 2010-08-15 00:38 <cedk> sharoon: I will put it back on the todo list | ||
| 2010-08-15 00:38 -!- carlos(~carlos@84.120.37.193.dyn.user.ono.com) has joined #tryton | ||
| 2010-08-15 00:38 <sharoon> cedk: lol, GTD! | ||
| 2010-08-15 00:39 <sharoon> cedk: we have to cater to multicompany in this object also | ||
| 2010-08-15 00:40 <sharoon> cedk: timesheet has company | ||
| 2010-08-15 00:40 <sharoon> cedk: so that should make this also compatible right? | ||
| 2010-08-15 00:41 <cedk> sharoon: company field will be inherited | ||
| 2010-08-15 00:41 <sharoon> cedk: updated http://piratepad.net/c789Qgxgfm | ||
| 2010-08-15 00:41 <sharoon> cedk: once we finalise on that i will update the blueprint | ||
| 2010-08-15 00:43 <sharoon> cedk: should we leave the field as party or should we make it owner? | ||
| 2010-08-15 00:44 <cedk> sharoon: it could be just renamed in view | ||
| 2010-08-15 00:44 <sharoon> cedk: so in model leave it as party | ||
| 2010-08-15 00:44 <cedk> sharoon: oops forget it | ||
| 2010-08-15 00:44 <cedk> sharoon: named it in the model owner or issuer ? | ||
| 2010-08-15 00:44 <cedk> or creator | ||
| 2010-08-15 00:45 <sharoon> cedk: it might be inconsistent, i think we could call it owner | ||
| 2010-08-15 00:45 <sharoon> cedk: ok changed | ||
| 2010-08-15 00:45 <sharoon> cedk: final word on priority? | ||
| 2010-08-15 00:46 <sharoon> cedk: can we leave the base module with simple static options of priority | ||
| 2010-08-15 00:47 <sharoon> cedk: the prefix should come from the sequence right? not in code | ||
| 2010-08-15 00:48 <cedk> sharoon: yes for sequence | ||
| 2010-08-15 00:48 <cedk> sharoon: I think that with a static priority it will be harder to extend it | ||
| 2010-08-15 00:49 <sharoon> cedk: a function field for a selection for which we will now give values from a method | ||
| 2010-08-15 00:49 <sharoon> this method could be inherited by other modules to change | ||
| 2010-08-15 00:50 <cedk> sharoon: there is per example company that will work on strict FIFO | ||
| 2010-08-15 00:50 <cedk> sharoon: so no need of priority | ||
| 2010-08-15 00:50 <sharoon> cedk: clear | ||
| 2010-08-15 00:51 <sharoon> cedk: so could be something for different modules to do | ||
| 2010-08-15 00:51 <sharoon> cedk: now to the representation of history | ||
| 2010-08-15 00:51 <sharoon> cedk: rather followups | ||
| 2010-08-15 00:51 <sharoon> cedk: which fields should be displayed in history? | ||
| 2010-08-15 00:53 <cedk> sharoon: i think in list view: writer, date, comment, state | ||
| 2010-08-15 00:53 <sharoon> cedk: assigned_to? | ||
| 2010-08-15 00:53 <cedk> sharoon: no | ||
| 2010-08-15 00:54 <cedk> sharoon: by writer is a little bit complicated | ||
| 2010-08-15 00:54 <sharoon> cedk: that might be something which changes also right? | ||
| 2010-08-15 00:54 <cedk> sharoon: yes but it will be for the form view | ||
| 2010-08-15 00:54 <sharoon> cedk: ok | ||
| 2010-08-15 00:55 <cedk> sharoon: but writer could be any one: a party, user, employee or even email | ||
| 2010-08-15 00:56 <sharoon> true! so how doe we handle that? | ||
| 2010-08-15 00:56 <cedk> sharoon: so I don't know how to handle it | ||
| 2010-08-15 00:56 <sharoon> cedk: easiest option is to have party | ||
| 2010-08-15 00:56 <sharoon> cedk: most generic | ||
| 2010-08-15 00:56 <sharoon> cedk: anyway, ticket email also has to resolve party | ||
| 2010-08-15 00:58 <sharoon> cedk: where will history get the value for writer? a last updated by field? | ||
| 2010-08-15 00:58 <cedk> sharoon: or a simple text field | ||
| 2010-08-15 00:59 <sharoon> cedk: simple char field could be the most generic | ||
| 2010-08-15 00:59 <cedk> sharoon: I think the field should be filled depending of the context | ||
| 2010-08-15 01:00 <cedk> sharoon: so a function will give to create/write the value | ||
| 2010-08-15 01:00 <cedk> sharoon: so when modification from GTK client -> take the user | ||
| 2010-08-15 01:00 <cedk> sharoon: when modification from email -> take the email | ||
| 2010-08-15 01:00 <cedk> sharoon: etc. | ||
| 2010-08-15 01:00 <sharoon> cedk: clear | ||
| 2010-08-15 01:01 <sharoon> cedk: so a new field for ticket model | ||
| 2010-08-15 01:01 <cedk> sharoon: yes but hidden in client | ||
| 2010-08-15 01:01 <sharoon> cedk: yep | ||
| 2010-08-15 01:04 <sharoon> cedk: does it look fine? | ||
| 2010-08-15 01:08 <sharoon> cedk: ping | ||
| 2010-08-15 01:09 <cedk> sharoon: made some changes | ||
| 2010-08-15 01:09 <sharoon> cedk: ok | ||
| 2010-08-15 01:10 <sharoon> cedk: it looks good to me now! | ||
| 2010-08-15 01:11 <sharoon> cedk: may be this could be the raw vblueprint into which we could commit improvements in terms of reports, graphs etc | ||
| 2010-08-15 01:11 <cedk> sharoon: if you want | ||
| 2010-08-15 01:12 <sharoon> cedk: are the menus OK in the original blueprint? | ||
| 2010-08-15 01:12 <cedk> sharoon: yes | ||
| 2010-08-15 01:13 <cedk> sharoon: I will add a tree view with state and tree_action to open tickets of the selected state | ||
| 2010-08-15 01:14 <sharoon> got you | ||
| 2010-08-15 01:15 <sharoon> cedk: updated wiki http://code.google.com/p/tryton/wiki/support_system | ||
| 2010-08-15 01:15 <sharoon> can you confirm if the menu i added is fine? | ||
| 2010-08-15 01:16 <sharoon> Tickets by State | ||
| 2010-08-15 01:18 <sharoon> cedk: looks done to me :) | ||
| 2010-08-15 01:19 <cedk> sharoon: for product patch, you did not write the exact comment | ||
| 2010-08-15 01:19 <sharoon> sorry checking! | ||
| 2010-08-15 01:20 <cedk> sharoon: just one menu "New Ticket" | ||
| 2010-08-15 01:21 <sharoon> cedk: ok | ||
| 2010-08-15 01:21 <sharoon> cedk: updated wiki | ||
| 2010-08-15 01:25 <cedk> sharoon: seems good | ||
| 2010-08-15 01:25 <cedk> sharoon: maybe sent an email on tryton-dev for review | ||
| 2010-08-15 01:25 <sharoon> cedk: fixed the product patch also | ||
| 2010-08-15 01:25 <sharoon> cedk: yes | ||
| 2010-08-15 01:29 <sharoon> cedk: done | ||
| 2010-08-15 01:29 <sharoon> ACTION Got to go 4 supper! Bye all | ||
| 2010-08-15 01:29 <sharoon> cedk: bye, good night | ||
| 2010-08-15 01:31 <cedk> sharoon: bye | ||
| 2010-08-15 01:31 -!- sharoon(~sharoon@vpn103.its.manchester.ac.uk) has left #tryton | ||
| 2010-08-15 01:41 -!- woakas(~woakas@pcsp163-59.supercabletv.net.co) has joined #tryton | ||
| 2010-08-15 03:17 -!- juanfer(~juanfer@186.28.70.65) has joined #tryton | ||
| 2010-08-15 03:46 -!- digitalsatori(~tony@116.233.241.200) has joined #tryton | ||
| 2010-08-15 05:20 -!- yangoon(~mathiasb@p549F7D35.dip.t-dialin.net) has joined #tryton | ||
| 2010-08-15 06:53 -!- digitalsatori(~tony@116.233.241.200) has joined #tryton | ||
| 2010-08-15 11:29 -!- digitalsatori(~tony@116.233.241.200) has joined #tryton | ||
| 2010-08-15 12:10 -!- sharoon(~sharoon@opg066b.halls.manchester.ac.uk) has joined #tryton | ||
| 2010-08-15 12:42 -!- Coldfire(~Coldfire@112.115.218.102) has joined #tryton | ||
| 2010-08-15 12:43 <Coldfire> hey, guys, i am chinese, and i am new to tryton and want do some translation first | ||
| 2010-08-15 12:43 <Coldfire> any tell me where to start | ||
| 2010-08-15 12:44 <cedk> Coldfire: here is the howto http://code.google.com/p/tryton/wiki/HowtoTranslate | ||
| 2010-08-15 12:48 <Coldfire> ok, thx | ||
| 2010-08-15 13:20 -!- Coldfire(~Coldfire@112.115.218.102) has joined #tryton | ||
| 2010-08-15 14:31 -!- FWiesing(~FWiesing@85-126-100-130.work.xdsl-line.inode.at) has joined #tryton | ||
| 2010-08-15 14:43 -!- sharoon(~sharoon@vpn70.its.manchester.ac.uk) has joined #tryton | ||
| 2010-08-15 16:56 -!- eLBati(~elbati@94.160.90.85) has joined #tryton | ||
| 2010-08-15 17:07 -!- eLBati(~elbati@94.160.55.229) has joined #tryton | ||
| 2010-08-15 18:40 -!- sharkcz(~sharkcz@2001:15c0:6747:160::7) has joined #tryton | ||
| 2010-08-15 19:19 -!- evernichon(~evernicho@goy81-2-88-180-146-31.fbx.proxad.net) has joined #tryton | ||
| 2010-08-15 20:33 -!- enlightx(~enlightx@95.75.207.221) has joined #tryton | ||
| 2010-08-15 21:29 -!- sharoon(~sharoon@vpn11.its.manchester.ac.uk) has joined #tryton | ||
| 2010-08-15 21:57 -!- Timitos(~kp@88.217.184.172) has joined #tryton | ||
| 2010-08-15 23:42 -!- eLBati(~elbati@94.161.25.14) has joined #tryton | ||
| 2010-08-15 23:56 -!- paepke(~paepke@p4FEB5CE5.dip.t-dialin.net) has joined #tryton |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!