Batch Modify plugin
Roger Oberholtzer
is enabled. I have added TICKET_BATCH_MODIFY to anonymous' permissions.
However, when I view a report, the batch modify stuff at the bottom of
the page is greyed out. All except the Comment field. It shows all the
fields, but I cannot change anything. What did I miss? Anyone else see
this problem?
I also see that there are some outstanding bugs files for this
(http://trac-hacks.org/ticket/4928) that may be related to this. Is this
plugin maintained?
jevans
On Jun 30, 8:18 am, Roger Oberholtzer <roger.oberholt...@gmail.com>
wrote:
Does it show check boxes next to each field and are you able to check
them? If so, that should enable the fields you check.
- jevans
Roger Oberholtzer
> Hi Roger,
> Does it show check boxes next to each field and are you able to check
> them? If so, that should enable the fields you check.
There are check boxes. But for things like the milestone, the menu is
empty and cannot be selected. For others where you could enter text,
the text entry cannot be selected. All are that way. Except the
Comment field.
--
Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB
Kapellgränd 7
P.O. Box 4205
SE-102 65 Stockholm, Sweden
Office: Int +46 8-615 60 20
Mobile: Int +46 70-815 1696
Roger Oberholtzer
> Hi Roger,
> Does it show check boxes next to each field and are you able to check
> them? If so, that should enable the fields you check.
The check boxes work. But I cannot do anything in the fields themselves.
Like enter text in a field, or select a milestone. The only exception is
the Comment field, which acts as expected.
jevans
On Jul 1, 12:55 am, Roger Oberholtzer <roger.oberholt...@gmail.com>
wrote:
the same options as when editing an individual ticket (just doesn't/
can't show 'current' values). I don't know reasons it might not work
for you. We have Trac 0.11.4 and latest 0.11 Batch Modify plug-in.
- jevans
Roger Oberholtzer
I understand about not being able to show current values, as they may be
different for each ticket.
I have trac 0.12multirepos from 2009-05-19, as well as the current
plug-in.
yoheeb
> On Wed, 2009-07-01 at 06:53 -0700, jevans wrote:
>
> > On Jul 1, 12:55 am, Roger Oberholtzer <roger.oberholt...@gmail.com>
> > wrote:
> > > On Tue, 2009-06-30 at 12:21 -0700, jevans wrote:
> > > > Hi Roger,
> > > > Does it show check boxes next to each field and are you able to check
> > > > them? If so, that should enable the fields you check.
>
> > > The check boxes work. But I cannot do anything in the fields themselves.
> > > Like enter text in a field, or select a milestone. The only exception is
> > > the Comment field, which acts as expected.
>
thread just like this before I finally realized what everyone meant.
have you checked a check box NEXT TO A TICKET in the query results to
"batch modify" ?
in other words, you have to check at least 2 boxes, one to the left of
a ticket #(really More than one why would you "batch modify" a single
ticket?), and then the field you want to modify (say, milestone).
Again, it seems obvious, but I was a knucklehead until it finally
clicked.
Also, I have found that for some reason I need to occasionally need to
navigate away from trac, force firefox to clear it's cache, then
restart it and the check boxes next to the tickets (which I alluded to
above) magically appear. since by default, NONE of the query results
are select to apply the changes to, and the darn check boxes next to
the individual tickets just weren't present. I am guessing this might
be your case. you never have seen those checkboxes next to each
ticket ID everyone is talking about.
Of course, it could just be not working for you.
Roger Oberholtzer
> in other words, you have to check at least 2 boxes, one to the left of
> a ticket #(really More than one why would you "batch modify" a single
> ticket?), and then the field you want to modify (say, milestone).
> Again, it seems obvious, but I was a knucklehead until it finally
> clicked.
This had occurred to me. I selected three or so tickets. Maybe there is
a browser problem with the javascript involved? I tried Firefox 3.5,
Konqueror 4.3, and IExplorer 6.0 (at work - they keep this version). All
act the same.
> Also, I have found that for some reason I need to occasionally need to
> navigate away from trac, force firefox to clear it's cache, then
> restart it and the check boxes next to the tickets (which I alluded to
> above) magically appear. since by default, NONE of the query results
> are select to apply the changes to, and the darn check boxes next to
> the individual tickets just weren't present. I am guessing this might
> be your case. you never have seen those checkboxes next to each
> ticket ID everyone is talking about.
I tried re-starting the browser. No joy.
I am guessing there is something in 0.12multirepos that is not in the
0.11 everyone happily using this plug-in are using.
yoheeb
> I tried re-starting the browser. No joy.
>
> I am guessing there is something in 0.12multirepos that is not in the
> 0.11 everyone happily using this plug-in are using.
and private sessions, after navigating away from the trac sites, then
close and start back up. closing the browser was insufficient.
Despite having the browser set to clear automatically on exit. I have
no idea why. This is in Firefox. Has always been an issue for some
reason. I still have to do it sometimes. I also see sometimes if I
select too many tickets, the changes don't seem to apply. If I reduce
the ticket count until I can apply, all the original request changes
show up in the browser, and I don't get the error message with it.
Weird, but it "works" But yes, I am on 0.11, so could be.
Roger Oberholtzer
I quit the browser and restarted the apache server. I also tried at
home with a different computer (MAC OS with Safari). No joy. I am
leaning toward a 0.12multirepos issue. Maybe I can find a message in a
log somewhere. Anyone have any ideas?
--
Roger Oberholtzer