[Trac] Re: Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
Hi, Am Donnerstag, 6. Februar 2014 10:22:38 UTC+1 schrieb Kristian Nørgaard: 3. Interpret "estimatedhours" as a fixed field, in the meaning of "INITIAL > estimated total time". > I use this approach. I use 3 additional custom fields with the following meaning: 1. estimatedhours.label = originally planned time 2. remaininghours.label = currently estimated rest time 3. totalhours.label = sum of worked time > This doesn't make much sense for the various graphs unless you add another > custom field "remaininghours" to mean the "recently estimated remaining > time". > > But this solution does still not provide consistent interpretation: > > a) For custom queries TimingAndEstimationPlugin still sums up > "estimatedhours" - "totalhours", so this number will often be different > from the field "remainingtime" (though they claim to give you the same > information) > Not sure what you mean. Where does it sum up that difference? I just know the sum up in the ticket query result table but each column has it's own sum there, and there's no subtraction. > b) Also TracJsGanttPlugin can not show the actual situation since no > single field provides the "currently estimated total time" which would be > the input it needs for "fields.estimate" > I use a patch to TracJsGanttPlugin I've posted in https://trac-hacks.org/ticket/11549 now. The chart is computed based on the remaininghours, but the ticket bar length is equal to the estimatedhours. The inner black bar is totalhours against estimatedhours in percent. CU, F@lk -- 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.
[Trac] Re: default_descrip.txt
Thank you so much for your reply. I will do as you suggest and review the changes between the versions. On Tuesday, February 4, 2014 9:13:26 AM UTC-6, ONeal Freeman wrote: > > Our office is upgrading from Trac 0.10.4 running on a linux server to Trac > 1.0.1 running on windows. The original version used > /conf/default_descrip.txt to add some additional sections to the > description portion of a new ticket. I cannot see how this works or a line > in a conf file that directs to the txt file. Can 1.0.1 still use this file? > Thanks. > -- 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.
[Trac] Re: plugin install trouble
Downgrading to SVN 1.6.23 seems to fix these issues.
--
S T I M U L A N T
Josh Santangelo, Technical Director
P 206 737 5601 / HQ 415 255 7081 / T @stimulant
On Tue, Feb 4, 2014 at 11:40 AM, Josh Santangelo wrote:
> I'm trying to install a couple of plugins (tried
> both TracIniAdminPanelPlugin and IniAdminPlugin), but having trouble. I've
> installed things successfully with easy_install before, but these are both
> dying for me with similar errors. This leads me to believe that it's a
> system/python configuration problem, not an issue with the plugins. Being
> new to the python world, I'm unsure what to try next. Logs below.
>
> thanks,
> -josh
>
> TracIniAdminPanelPlugin:
>
> C:\tracwork\iniadmin>easy_install
> http://trac-hacks.org/svn/traciniadminpanelplugin/trunk/
> Downloading http://trac-hacks.org/svn/traciniadminpanelplugin/trunk/
> Doing subversion checkout from
> http://trac-hacks.org/svn/traciniadminpanelplugin/trunk/ to c:\users\
> trac\appdata\local\temp\easy_install-2nex1r\trunk
> Processing trunk
> Running setup.py -q bdist_egg --dist-dir
> c:\users\trac\appdata\local\temp\easy_install-2nex1r\trunk\
> egg-dist-tmp-rv8b1o
> Traceback (most recent call last):
> File "C:\Python27\Scripts\easy_install-script.py", line 8, in
> load_entry_point('setuptools==0.6c11', 'console_scripts',
> 'easy_install')()
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 1712, in main
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 1700, in with_ei_usage
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 1716, in
> File "C:\Python27\lib\distutils\core.py", line 152, in setup
> dist.run_commands()
> File "C:\Python27\lib\distutils\dist.py", line 953, in run_commands
> self.run_command(cmd)
> File "C:\Python27\lib\distutils\dist.py", line 972, in run_command
> cmd_obj.run()
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 211, in run
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 422, in easy_install
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 476, in install_item
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 655, in install_eggs
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 930, in build_and_install
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\easy_install.py
> ", line 919, in run_setup
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\sandbox.py",
> line 62, i
> n run_setup
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\sandbox.py",
> line 105,
> in run
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\sandbox.py",
> line 64, i
> n
> File "setup.py", line 60, in
> File "C:\Python27\lib\distutils\core.py", line 152, in setup
> dist.run_commands()
> File "C:\Python27\lib\distutils\dist.py", line 953, in run_commands
> self.run_command(cmd)
> File "C:\Python27\lib\distutils\dist.py", line 971, in run_command
> cmd_obj.ensure_finalized()
> File "C:\Python27\lib\distutils\cmd.py", line 109, in ensure_finalized
> self.finalize_options()
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\bdist_egg.py",
> line 94, in finalize_options
> File "C:\Python27\lib\distutils\cmd.py", line 312, in
> get_finalized_command
> cmd_obj.ensure_finalized()
> File "C:\Python27\lib\distutils\cmd.py", line 109, in ensure_finalized
> self.finalize_options()
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\egg_info.py",
> l
> ine 85, in finalize_options
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\egg_info.py",
> l
> ine 185, in tags
> File
> "C:\Python27\lib\site-packages\setuptools-0.6c11-py2.7.egg\setuptools\command\egg_info.py",
> l
> ine 233, in get_svn_revision
> IndexError: list index out of range
>
> IniAdminPlugin:
>
> C:\tracwork\iniadmin>easy_install
> http://trac-hacks.org/svn/iniadminplugin/0.11
> Downloading http://trac-hacks.org/svn/iniadminplugin/0.11
> Doing subversion checkout from
> http://trac-hacks.org/svn/iniadminplugin/0.11 to c:\users\trac\appdat
> a\local\temp\easy_install-wlxaro\0.11
> Processing 0.11
> Running setup.py -q bdist_egg --dist-dir
> c:\users\trac\appdata\local\temp\easy_install-wlxaro\0.11\e
> gg-dist-tmp-6wlgs4
> Traceback (most recent call last):
> File "C:\Python27\Scripts\easy_install-script.py", line 8, in
> load_entry_point('setupt
Re: [Trac] Re: Accidentally deleted the report while editing the sql query
On Thu, Feb 6, 2014 at 10:36 AM, Ethan Jucovy wrote: > On Thu, Feb 6, 2014 at 9:32 AM, Soha wrote: > >> Hi, >> >> Looks like I have given the wrong workflow. Please consider the below one >> : >> >> analyze = new_ticket -> assign_severity_and_analyze >> analyze.default = 999 >> analyze.operation = set_owner_to_self >> analyze.permissions = TICKET_CREATE >> assign = assign_severity_and_analyze -> triage_and_assignment >> assign.default = 996 >> assign.operation = set_owner >> assign.permission = TICKET_MODIFY >> close = user_test -> closed >> close.default = 994 >> close.operation = set_owner >> close.permissions = TICKET_CREATE >> fix = triage_and_assignment -> fix >> fix.default = 995 >> fix.operation = set_owner >> fix.permissions = TICKET_MODIFY >> leave = closed -> * >> >> leave.default = 1000 >> leave.operations = leave_status >> reopen = unit_test,user_test -> triage_and_assignment >> reopen.default = 992 >> reopen.operation = del_resolution >> reopen.permissions = TICKET_CREATE >> resolved = triage_and_assignment -> closed >> resolved.default = 993 >> resolved.operation = set_resolution >> resolved.permissions = TICKET_MODIFY >> test = fix -> unit_test >> test.default = 997 >> test.operation = set_owner >> test.permissions = TICKET_MODIFY >> uat = unit_test -> user_test >> uat.default = 998 >> uat.operation = set_owner >> uat.permissions = TICKET_MODIFY >> > > The 'Warning : The action view is not available".' message would appear > if you POST a ticket form (modifying the ticket and/or leaving a comment) > that doesn't contain an "action" parameter. But I'm not sure why that > would be happening if you're using Trac's built in user interface. > > One problem: you have "analyze = new_ticket -> > assign_severity_and_analyze". But "new_ticket" isn't a new ticket's > starting state -- that should be "new". Right now you have no workflow > actions attached to the "new" state, which all newly created tickets start > out in. So, any time you're trying to leave a comment or modify the > ticket, it seems like there are no valid actions that can be taken. > > There seems to be more going on here -- I think ConfigurableTicketWorkflow > is supposed to provide a "_reset" action for cases like this, which should > be submitted in the POST request instead of nothing being posted. Unless > you have other plugins installed which are changing the behavior of the > ticket modify form. > For future reference: I can reproduce the problem using the above workflow configuration on a new trac environment. I'm going to look into this a bit to figure out why "_reset" isn't kicking in. I'll file a core ticket if it seems appropriate once I understand a bit more about what's going on. -Ethan -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
Thank You guys I am able to modify/close the ticket now. I really appreciate for all the help. On Thursday, February 6, 2014 10:43:18 AM UTC-5, RjOllos wrote: > > Yeah that new_ticket state looks suspicious. Nice catch! -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
Yeah that new_ticket state looks suspicious. Nice catch! -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
Please set TracLogging to DEBUG, restart the web server and perform the operations that lead to the warning; then send along the content of the log. -- 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.
Re: [Trac] Re: Accidentally deleted the report while editing the sql query
On Thu, Feb 6, 2014 at 9:32 AM, Soha wrote: > Hi, > > Looks like I have given the wrong workflow. Please consider the below one : > > analyze = new_ticket -> assign_severity_and_analyze > analyze.default = 999 > analyze.operation = set_owner_to_self > analyze.permissions = TICKET_CREATE > assign = assign_severity_and_analyze -> triage_and_assignment > assign.default = 996 > assign.operation = set_owner > assign.permission = TICKET_MODIFY > close = user_test -> closed > close.default = 994 > close.operation = set_owner > close.permissions = TICKET_CREATE > fix = triage_and_assignment -> fix > fix.default = 995 > fix.operation = set_owner > fix.permissions = TICKET_MODIFY > leave = closed -> * > > leave.default = 1000 > leave.operations = leave_status > reopen = unit_test,user_test -> triage_and_assignment > reopen.default = 992 > reopen.operation = del_resolution > reopen.permissions = TICKET_CREATE > resolved = triage_and_assignment -> closed > resolved.default = 993 > resolved.operation = set_resolution > resolved.permissions = TICKET_MODIFY > test = fix -> unit_test > test.default = 997 > test.operation = set_owner > test.permissions = TICKET_MODIFY > uat = unit_test -> user_test > uat.default = 998 > uat.operation = set_owner > uat.permissions = TICKET_MODIFY > The 'Warning : The action view is not available".' message would appear if you POST a ticket form (modifying the ticket and/or leaving a comment) that doesn't contain an "action" parameter. But I'm not sure why that would be happening if you're using Trac's built in user interface. One problem: you have "analyze = new_ticket -> assign_severity_and_analyze". But "new_ticket" isn't a new ticket's starting state -- that should be "new". Right now you have no workflow actions attached to the "new" state, which all newly created tickets start out in. So, any time you're trying to leave a comment or modify the ticket, it seems like there are no valid actions that can be taken. There seems to be more going on here -- I think ConfigurableTicketWorkflow is supposed to provide a "_reset" action for cases like this, which should be submitted in the POST request instead of nothing being posted. Unless you have other plugins installed which are changing the behavior of the ticket modify form. But I think changing that line in trac.ini to `analyze = new -> assign_severity_and_analyze` would probably fix this problem. -Ethan -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
It is mentioned as workflow = ConfigurableTicketWorkflow On Thursday, February 6, 2014 10:13:33 AM UTC-5, RjOllos wrote: > > I'm referring to the workflow option in the [ticket] section of trac.ini -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
I'm referring to the workflow option in the [ticket] section of trac.ini -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
Hi,
Looks like I have given the wrong workflow. Please consider the below one :
analyze = new_ticket -> assign_severity_and_analyze
analyze.default = 999
analyze.operation = set_owner_to_self
analyze.permissions = TICKET_CREATE
assign = assign_severity_and_analyze -> triage_and_assignment
assign.default = 996
assign.operation = set_owner
assign.permission = TICKET_MODIFY
close = user_test -> closed
close.default = 994
close.operation = set_owner
close.permissions = TICKET_CREATE
fix = triage_and_assignment -> fix
fix.default = 995
fix.operation = set_owner
fix.permissions = TICKET_MODIFY
leave = closed -> *
leave.default = 1000
leave.operations = leave_status
reopen = unit_test,user_test -> triage_and_assignment
reopen.default = 992
reopen.operation = del_resolution
reopen.permissions = TICKET_CREATE
resolved = triage_and_assignment -> closed
resolved.default = 993
resolved.operation = set_resolution
resolved.permissions = TICKET_MODIFY
test = fix -> unit_test
test.default = 997
test.operation = set_owner
test.permissions = TICKET_MODIFY
uat = unit_test -> user_test
uat.default = 998
uat.operation = set_owner
uat.permissions = TICKET_MODIFY
And what do you mean by value of {ticket} workflow ?
On Thursday, February 6, 2014 5:25:45 AM UTC-5, RjOllos wrote:
>
> On Wednesday, February 5, 2014 3:09:48 PM UTC-8, Soha wrote:
>>
>> Here is the workflow :
>>
>> [ticket-workflow]
>> accept = new -> accepted
>> accept.default = 997
>> accept.operations = set_owner_to_self
>> accept.permissions = TICKET_MODIFY
>> leave = accepted,new,assigned,closed -> *
>> leave.default = 1000
>> leave.operations = leave_status
>> reassign = accepted,assigned,test -> assigned
>> reassign.default = 999
>> reassign.operations = set_owner
>> reassign.permissions = TICKET_MODIFY
>> reopen = closed -> assigned
>> reopen.default = 996
>> reopen.operations = del_resolution
>> reopen.permissions = TICKET_CREATE
>> resolve = accepted,new,test -> closed
>> resolve.default = 998
>> resolve.operations = set_resolution
>> resolve.permissions = TICKET_MODIFY
>> verify = assigned -> test
>> verify.default = 995
>> verify.permissions =
>>
>>
>> {ticket-custom}
>>
>> blockedby = text
>> blockedby.label = Blocked By
>> blocking = text
>> blocking.label = Blocking
>> data_set = text
>> data_set.label = Data Set
>> dependencies = text
>> dependencies.label = Dependencies
>> development_status = select
>> development_status.label = Development Status
>> development_status.options = Under Review|Fix in Progress|Fixed
>> development_status.value = two
>> due_assign = text
>> due_assign.label = Due to assign
>> due_assign.value = DD/MM/
>> due_close = text
>> due_close.label = Due to close
>> due_close.value = DD/MM/
>> expected_reslts.cols = 250
>> expected_results = text
>> expected_results.label = Expected Results
>> expected_results.rows = 60
>> expected_results.value =
>> planid = text
>> planid.label = Test Plan
>> scenario = text
>> scenario.label = Scenario
>> steps_to_perform_test = text
>> steps_to_perform_test.cols = 60
>> steps_to_perform_test.label = Steps to perform test
>> steps_to_perform_test.rows = 30
>> steps_to_perform_test.value =
>> test_case_comments = text
>> test_case_comments.label = Test Case Comments
>> test_case_execution_result = radio
>> test_case_execution_result.label = Test Case Execution Result
>> test_case_execution_result.options = Pass|Fail
>> test_case_execution_result.value = dos
>> test_results_comments = text
>> test_results_comments.label = Test Results Comments
>> test_results_v_05 = text
>> test_results_v_05.cols = 250
>> test_results_v_05.label = Test Results V.05
>> test_results_v_05.rows = 60
>> test_results_v_06 = text
>> test_results_v_06.cols = 250
>> test_results_v_06.label = Test Results V.06
>> test_results_v_06.rows = 60
>> testcaseid = text
>> testcaseid.label = Test Case
>> testscenario = text
>> testscenario.label = Test Scenario
>>
>> But I didn't do anything to the workflow that issue started ever since
>> the report1 got deleted. Please let me know.
>>
>> Thanks for your prompt responses.
>>
>> On Wednesday, February 5, 2014 4:48:24 PM UTC-5, RjOllos wrote:
>>>
>>> On Wednesday, February 5, 2014 8:30:36 AM UTC-8, Soha wrote:
Hi,
I was trying to modify a sql query for a report and somehow the report
got deleted. I am not able to use the "view tickets" tab as the page was
directing to report1 which got deleted. So I went to the next report and
also changed the page to link to report2 in the trac.ini page. Now we are
able to view the ticket page but not able to modify/close them. It is
giving the error as " Warning : The action view is not available".
Please help me fix this issue as it is a major issue for us now. I
think there is no way to retrieve the deleted report. Is there a way to
get
rid of this error : " Warning : The action view is not available".
>>>
>>> The warning is related to the ticket workfl
Re: [Trac] Re: New users Help needed
On 02/06/2014 07:28 AM, RjOllos wrote: PS : there is a bug with log in / log out : While connected as a classique user, I loggout , and while trying to logging again, Trac autmaticcaly log me, instead of give the choice of loggin / password as another user (admin for instance ..). This is a known issue with browser (not Trac): http://trac.edgewall.org/ticket/791 In addition to many other useful features, the AccountManagerPlugin (http://trac-hacks.org/wiki/AccountManagerPlugin) adds an HTML form-based login which works around this issue. -- Matthew Caron, Software Build Engineer Red Lion Controls | www.redlion.net +1 (518) 877-5173 x138 office -- 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.
Re: [Trac] Accidentally deleted the report while editing the sql query
On 02/05/2014 11:30 AM, Soha wrote: Please help me fix this issue as it is a major issue for us now. I think there is no way to retrieve the deleted report. Sure there is - you restore it from the nightly DB snapshot you made either by copying the sqlite DB, or using pg_dump. Here is an example postgres backup script: #!/bin/bash if [ `whoami` != 'postgres' ]; then echo "Please run this as user postgres"; exit 255; fi FILE=$(mktemp /opt/trac/eng/db/postgres.bak.`date +%F`.XX) if [ "$?" -eq "0" ]; then pg_dump trac > $FILE && lzma $FILE; fi cron that bad Larry, and you're good to go. (And, if you're not doing this, you must enjoy living dangerously.) -- Matthew Caron, Software Build Engineer Red Lion Controls | www.redlion.net +1 (518) 877-5173 x138 office -- 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.
Re: [Trac] Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
On 02/06/2014 04:22 AM, Kristian Nørgaard wrote: *In what way should I use and interpret "estimatedhours"?* I have tried 3 different approaches: 1. Interpret "estimatedhours" as a dynamically changed field, in the meaning of "most recently estimated TOTAL time" It seems odd to re-estimate with a total time, maybe you already worked 100 hours on a ticket, then the obvious thing you want to do is estimate how many hours are left (not the total). This is how we use it. It may seem odd to you, but never seemed odd to us, so the oddity is not universal. 3. Interpret "estimatedhours" as a fixed field, in the meaning of "INITIAL estimated total time". This doesn't make much sense for the various graphs unless you add another custom field "remaininghours" to mean the "recently estimated remaining time". Our reports often find the first change to the estimatedhours field which makes it a nonzero value, for estimate accuracy analysis at project end. In a sense, this is a derived value. So either I am not understanding these things right or everyone is just accepting to live with such inconsistencies? We don't see 1 as an inconsistency. -- Matthew Caron, Software Build Engineer Red Lion Controls | www.redlion.net +1 (518) 877-5173 x138 office -- 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.
[Trac] Re: New users Help needed
On Thursday, February 6, 2014 4:14:36 AM UTC-8, Guillaume M. wrote: > > Dear all, > > > I'm a new user user to trac, and I would like to use it to follow all > projet we are working on it. > > I would be very grateful if you could give me some links where I could > find some information about "hacking" trac > so as to better fit my needs : > Most of the information you are requesting can be found in the TracGuide: http://trac.edgewall.org/wiki/TracGuide > - how to configure milestone / roadmap > http://trac.edgewall.org/wiki/TracRoadmap > - how to manage several project at a time > http://trac.edgewall.org/wiki/TracMultipleProjects > - how to display a "todo" list for each project > Where would you like the TODO list to be displayed? Typically you'd use tickets to create tasks. > - is it possible to define a "template", so as each projet follow the same > organisation ? > You'll need to be more specific. The interface can be customized: http://trac.edgewall.org/wiki/TracInterfaceCustomization > - is it better to specify several projet within a given trac project, or I > have to build (unsing tracd) a new projet each time ? > It depends on many factors. Trac doesn't have true multiproject support. You can use the Component field for simple multiproject support. Plugins such as SimpleMultiprojectPlugin and the friendly fork Apache Bloodhound support multiple projects. http://trac-hacks.org/wiki/SimpleMultiProjectPlugin http://bloodhound.apache.org/ Trac supports multiple environments in a single instance, so you'd use trac-admin to create a new environment. You can share configuration across the projects: http://trac.edgewall.org/wiki/TracIni#GlobalConfiguration many thanks for your help. > > > PS : there is a bug with log in / log out : While connected as a classique > user, I loggout , and while trying to logging again, > Trac autmaticcaly log me, instead of give the choice of loggin / password > as another user (admin for instance ..). > This is a known issue with browser (not Trac): http://trac.edgewall.org/ticket/791 -- 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.
[Trac] New users Help needed
Dear all, I'm a new user user to trac, and I would like to use it to follow all projet we are working on it. I would be very grateful if you could give me some links where I could find some information about "hacking" trac so as to better fit my needs : - how to configure milestone / roadmap - how to manage several project at a time - how to display a "todo" list for each project - is it possible to define a "template", so as each projet follow the same organisation ? - is it better to specify several projet within a given trac project, or I have to build (unsing tracd) a new projet each time ? many thanks for your help. PS : there is a bug with log in / log out : While connected as a classique user, I loggout , and while trying to logging again, Trac autmaticcaly log me, instead of give the choice of loggin / password as another user (admin for instance ..). -- 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.
[Trac] Re: Accidentally deleted the report while editing the sql query
On Wednesday, February 5, 2014 3:09:48 PM UTC-8, Soha wrote:
>
> Here is the workflow :
>
> [ticket-workflow]
> accept = new -> accepted
> accept.default = 997
> accept.operations = set_owner_to_self
> accept.permissions = TICKET_MODIFY
> leave = accepted,new,assigned,closed -> *
> leave.default = 1000
> leave.operations = leave_status
> reassign = accepted,assigned,test -> assigned
> reassign.default = 999
> reassign.operations = set_owner
> reassign.permissions = TICKET_MODIFY
> reopen = closed -> assigned
> reopen.default = 996
> reopen.operations = del_resolution
> reopen.permissions = TICKET_CREATE
> resolve = accepted,new,test -> closed
> resolve.default = 998
> resolve.operations = set_resolution
> resolve.permissions = TICKET_MODIFY
> verify = assigned -> test
> verify.default = 995
> verify.permissions =
>
>
> {ticket-custom}
>
> blockedby = text
> blockedby.label = Blocked By
> blocking = text
> blocking.label = Blocking
> data_set = text
> data_set.label = Data Set
> dependencies = text
> dependencies.label = Dependencies
> development_status = select
> development_status.label = Development Status
> development_status.options = Under Review|Fix in Progress|Fixed
> development_status.value = two
> due_assign = text
> due_assign.label = Due to assign
> due_assign.value = DD/MM/
> due_close = text
> due_close.label = Due to close
> due_close.value = DD/MM/
> expected_reslts.cols = 250
> expected_results = text
> expected_results.label = Expected Results
> expected_results.rows = 60
> expected_results.value =
> planid = text
> planid.label = Test Plan
> scenario = text
> scenario.label = Scenario
> steps_to_perform_test = text
> steps_to_perform_test.cols = 60
> steps_to_perform_test.label = Steps to perform test
> steps_to_perform_test.rows = 30
> steps_to_perform_test.value =
> test_case_comments = text
> test_case_comments.label = Test Case Comments
> test_case_execution_result = radio
> test_case_execution_result.label = Test Case Execution Result
> test_case_execution_result.options = Pass|Fail
> test_case_execution_result.value = dos
> test_results_comments = text
> test_results_comments.label = Test Results Comments
> test_results_v_05 = text
> test_results_v_05.cols = 250
> test_results_v_05.label = Test Results V.05
> test_results_v_05.rows = 60
> test_results_v_06 = text
> test_results_v_06.cols = 250
> test_results_v_06.label = Test Results V.06
> test_results_v_06.rows = 60
> testcaseid = text
> testcaseid.label = Test Case
> testscenario = text
> testscenario.label = Test Scenario
>
> But I didn't do anything to the workflow that issue started ever since the
> report1 got deleted. Please let me know.
>
> Thanks for your prompt responses.
>
> On Wednesday, February 5, 2014 4:48:24 PM UTC-5, RjOllos wrote:
>>
>> On Wednesday, February 5, 2014 8:30:36 AM UTC-8, Soha wrote:
>>>
>>> Hi,
>>>
>>> I was trying to modify a sql query for a report and somehow the report
>>> got deleted. I am not able to use the "view tickets" tab as the page was
>>> directing to report1 which got deleted. So I went to the next report and
>>> also changed the page to link to report2 in the trac.ini page. Now we are
>>> able to view the ticket page but not able to modify/close them. It is
>>> giving the error as " Warning : The action view is not available".
>>> Please help me fix this issue as it is a major issue for us now. I
>>> think there is no way to retrieve the deleted report. Is there a way to get
>>> rid of this error : " Warning : The action view is not available".
>>>
>>
>> The warning is related to the ticket workflow. What is the
>> [ticket-workflow] section of your trac.ini?
>>
>
The warning is added here (1). I don't see how an error could come about
through deleting a report. What is the value of `[ticket] workflow`?
(1)
http://trac.edgewall.org/browser/branches/1.0-stable/trac/ticket/web_ui.py?rev=12322&marks=573-578#L558
--
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.
[Trac] Re: Need Guidance on Admin, Trac 0.12.5 (GUI-end)
On Thursday, February 6, 2014 2:05:44 AM UTC-8, Frankly3D wrote: > > Trac 0.12.5 > > I would like to be able to add the following to all > 'Newly created tickets': > > Unfortunately we cannot keep tickets open-ended. > If no one has accepted your ticket by 1st April 2014, > ticket will be closed as "No Volunteer". > > But in a way that end user cannot remove it while creating ticket. > > Which part of "Admin" would be most suitable if any. > You can add a notice like shown in (1). For a recipe on how to implement this see (2). Scroll down to about the 4th paragraph: "Example snippet of adding introduction text to the new ticket form (but not shown during preview):" Is that what you are looking to implement? (1) https://trac-hacks.org/newticket (2) http://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance -- 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.
[Trac] Need Guidance on Admin, Trac 0.12.5 (GUI-end)
Trac0.12.5 I would like to be able to add the following to all 'Newly created tickets': Unfortunately we cannot keep tickets open-ended. If no one has accepted your ticket by 1st April 2014, ticket will be closed as "No Volunteer". But in a way that end user cannot remove it while creating ticket. Which part of "Admin" would be most suitable if any. -- 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.
[Trac] Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
After some testing, I am beginning to feel that there is really no consistent way of configuring the plugins *TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin * *In what way should I use and interpret "estimatedhours"?* I have tried 3 different approaches: 1. Interpret "estimatedhours" as a dynamically changed field, in the meaning of "most recently estimated TOTAL time" It seems odd to re-estimate with a total time, maybe you already worked 100 hours on a ticket, then the obvious thing you want to do is estimate how many hours are left (not the total). 2. Interpret "estimatedhours" as a dynamically changed field, in the meaning of "most recently estimated REMAINING time" This breaks two things as far as I can tell: a) In the last row of a custom query, TimingAndEstimationPlugin takes care of summarizing the "estimatedhours" for any custom query. And in the same row, it provides a remaining time result also, which is "estimatedhours" - "totalhours", summarized for the query. Obviously this doesn't make sense if "estimatedhours" means remaining hours. b) TracJsGanttPlugin wants needs an input for an estimate of the full ticket. No field contains that number with this setup. 3. Interpret "estimatedhours" as a fixed field, in the meaning of "INITIAL estimated total time". This doesn't make much sense for the various graphs unless you add another custom field "remaininghours" to mean the "recently estimated remaining time". But this solution does still not provide consistent interpretation: a) For custom queries TimingAndEstimationPlugin still sums up "estimatedhours" - "totalhours", so this number will often be different from the field "remainingtime" (though they claim to give you the same information) b) Also TracJsGanttPlugin can not show the actual situation since no single field provides the "currently estimated total time" which would be the input it needs for "fields.estimate" So either I am not understanding these things right or everyone is just accepting to live with such inconsistencies? regards, Kristian -- 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.
Re: [Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Sorry, I will repost this last email in a new thread, since I realize the subject has changed. / Kristian On Wed, Feb 5, 2014 at 3:09 PM, Kristian Nørgaard wrote: > After some testing, I am beginning to feel that there is really no > consistent way of configuring the plugins TimingAndEstimationPlugin, > EstimationToolsPlugin and EstimationToolsPlugin > > I have been trying to use your suggestion of adding that extra field > "remaininghours" to have EstimationToolsPlugin and EstimationToolsPlugin > work from that. > > I end up with these issues: > > TimingAndEstimationPlugin, I believe, takes care of summarizing the > "estimatedhours" for any custom query. > And in the same row, it provides a remaining time result also, which is > "estimatedhours" - "totalhours", summarized for the query. > This "remaining time" will obviously quickly be inconsistent with an > independent, manual bookkeeping of "remaininghours". > > TracJsGanttPlugin wants some input for an estimate of the full ticket. So > it doesn't really make sense with a trac.ini definition like this: > > fields.estimate = remaininghours > fields.worked = totalhours > > It should really be > fields.estimate = remaininghours + totalhours > fields.worked = totalhours > > but I know that is not a legal configuration. > > ??? > > So either I am not understanding these things right or everyone is just > accepting to live with such inconsistencies? > > regards, > Kristian > > > > > > > > On Mon, Feb 3, 2014 at 1:43 PM, F@lk wrote: > >> Hi, >> >> Am Montag, 3. Februar 2014 12:00:07 UTC+1 schrieb Kristian Nørgaard: >> >>> Will I have to perform database hacks also, as described in >>> http://trac-hacks.org/ticket/8681 >>> ??? >>> >> >> the manual DB tweaking described in #8681 is just necessary in this >> situation: >> - firstly, you used only EstimationToolsPlugin with ticket field >> 'estimatedhours' in the meaning of "recently estimated rest time" >> - secondly, after a while you wanted to use also >> TimingAndEstimationPlugin or TracJsGanttPlugin and recognize they use >> 'estimatedhours' in the meaning of "originally planned time for the ticket" >> The issue reported in #8681 reports the clash of the meaning of that >> ticket-field, and suggests how you can overcome the problem. >> >> Kristian, the a good practice is to use these 3 ticket fields: >> [ticket-custom] >> totalhours = text >> totalhours.label = sum of worked time >> totalhours.value = 0 >> estimatedhours = text >> estimatedhours.label = originally planned time >> estimatedhours.value = 8 >> remaininghours = text >> remaininghours.label = currently estimated rest time >> remaininghours.value = 8 >> >> For example, estimatedhours could be 120 hours (your plan), and you have >> 100 totalhours (what you've worked so far), and you still judge 100 >> remaininghours (currently expected rest time). >> >> and T&E plugin also internally needs: >> hours = text >> hours.label = adds another time to totalhours >> hours.value = 0 >> >> Then the charts should properly work. >> >> CU, F@lk >> >> -- >> 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. >> > > -- 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.
