Hello again, On this list the convention is to reply in-line or at the bottom. It makes it easier to read through...
> On Monday, December 9, 2013 9:41:58 AM UTC+2, Cooke, Mark wrote: > > > -----Original Message----- > > From: trac-...@googlegroups.com <javascript:> On > > Behalf Of cris croslobski > > Sent: 08 December 2013 10:37 > > > > HI, > > > > I am a new user in this bug tracking tool. > > Welcome! > > > I have some questions, can you please help me? > > > > 1. How can I customize tab with specific fields which I need > > to define in each tab? > > I am not certain of what you want, here. Which "tab"? > Do you mean on the ticket view? You can define "custom > fields", either through the trac.ini or via plugin(s): > > http://trac.edgewall.org/wiki/TracTicketsCustomFields > > Also: some of the existing fields can be hidden (if you > do not want them) by removing all the pre-configured values > via the Admin tab. > > > 2 .How can I use actions? I read the guide but I don't know > > how to go back to predefined action > > for example: I need 4 actions: submit, assign, resolve, close > > submit will change into assign, assign change to resolve, > > from resolve I need to go back to assign, and from close into > > resolve again. > > Read the workflow page:- > http://trac.edgewall.org/wiki/TracWorkflow > > Then try to build your own workflow ini and run it > through the online graphical visualiser (linked just above > the "Adding optional Testing with Workflow" section). If you > are still struggling, post a more specific question with what > you already tried... > > > 3. How can I use mandatories of the fields? > > ...you mean "not let people submit a ticket if specific > fields have not been completed"? Not sure but I believe > there are plugins that can help with that. Have you searched > trac-hacks? > > http://trac-hacks.org/ > > > 4. How can I update the data from external API script I > > preferred perl? > > There is a plugin that exposes an API:- > > http://trac-hacks.org/wiki/XmlRpcPlugin > > > 5. I see in the issue tracking only modify action, How can I > > choose the one I want? > > ...the available options depend on transitions defined > in the workflow from the current state, combined with the > associated permissions. Read the workflow page again. > > > 6. How can I use dependency of fileds, for example, when I > > will change the priority to major then field owner_name > > will change to (predefined user)? > > Not in "vanilla" trac but there may be a plugin for that. > > > Thank you for advance. > > I hope that helps you get started. The workflow stuff > is not too hard to understand it (I managed it so it must be > easy) once you have read it a few times and put stuff through > the visualiser. Otherwise, please try to be a bit more > descriptive in your questions, for example you have not told > us what platform you are on, which version of trac you have > installed or that most of your questions seem to relate only > to the ticket page (unless I guess wrong) but there is quite > a bit more to trac than tickets (wiki, source integration, > misc plugins etc). > > Good luck! > > ~ Mark C > > -----Original Message----- > From: trac-users@googlegroups.com On Behalf Of cris croslobski > Sent: 09 December 2013 09:30 > > Hi Mark, > > Thank you. > > > I am using trac on windows to examine the tool, Trac 1.0. Ok, I have not yet migrated to 1.0 due to other major upgrades going on (soon, I hope). > 1. In the other bug tracking tool we in, I have 3 tabs, in > each tab I have 4 fields: > Tab1: priority, product, owner_t, submitter > Tab2: result, result_owner, test result, bypass > Tab3 : bug, type, owner_b, computer > I need a way to add a new ticket, the user will choose the > right tab and will write the values, in the ticket. You should probably not want Trac to be a clone of your other tool (or it would not be Trac), so UI details like tabs will be different. To add a new ticket just click on the "New Ticket" link (if you have permission but I assume you have given yourself TRAC_ADMIN for now) and fill in the details. Note that some are assumed (like 'submitter') or auto-populated (like 'version') based on configuration. > 2. Let take the basic cenario > > I don't know how can I configure these line to go back from > resolve to open. > > resolve_accepted = open,assigned,accepted -> closed > resolve_accepted.name = resolve > resolve_accepted.permissions = TICKET_MODIFY > resolve_accepted.operations = set_resolution The workflow defines the *transitions* and the *states* are derived from the start and end points of all the transitions. So to go back from "resolve" (actually "closed" from your example) to "open" you would need something like: reopen = closed -> open reopen.name = reopen reopen.permissions = TICKET_MODIFY > 5. When I add a new ticket I see only the next state, I need > to choose from 3 states: suppose I open a new ticket, I need > a way that the user will choose from 3 state: (assign, > resolve, or close) ...you need to update the *transitions* in the workflow. As I said before, try taking your existing workflow (or one of the examples in the documentation) and tweak it. Then run it through the visualiser to see if you get the right results. Rinse and repeat (as they say on shampoo bottles)... Each named *transition* lists all the valid "from" *states" and the single "to" *state*, so your three *transitions* ("assign", "resolve" and "close") all need to include *new* in their definition... > 3. How can I add a new plugin? The documentation at both trac.edgewall.org (teo) and trac-hacks.org (tho) explain this: teo: http://trac.edgewall.org/wiki/TracPlugins tho: http://trac-hacks.org/wiki/XmlRpcPlugin#Installation > 4.For the external I look for a api from perl only. What do you want to do with your scripts? How are you expecting this to work? Trac is a web-based tool, so you need to write your scripts to use whatever web interface Trac provides, e.g. XMLRPC (there may be others?) Trac itself is written in python, if you want to extend trac then this is a good opportunity to learn another language! > Thank you You are welcome. ~ Mark C -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
