Greetings,
After upgrading to 3.2.2 from 3.0.8 I noticed that Bulk Update behaves
in a different way then it used to. Previously when one would search for
tickets and limit the search results by 10 per page, then could click
bulkupdate link (Update All These Tickets at Once) and see the page of
10 tickets to pick from. Currently a search limited to 10 tickets per
page will produce reulsts with 10 items per page, though after selecting
Bulk Update the page comes up with entire ticket list from the search -
i.e. one page with 300+ or as many tickets as it happend to find
according to criteria in the search. This same behavior is also present
in 3.3.10.
3.2.2 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.11
MySQL 4.0.17
3.3.10 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.12
Has anyone noticed similar behavior or am I alone here?
Sincerely,
Alex Rebrik.
P.S. For now to work-around this issue I’ve dropped some quick Java
script to “de-select” all tickets in BulkUpdate with one click (in our
case 300+ tickets usually turn up on a search with status=New /
ower=Nobody / queue=MainQueue) this isn’t the preferred way however.
I’m pretty sure it always worked that way…On Fri, Oct 29, 2004 at 04:32:52PM -0700, Alex Rebrik wrote:
Greetings,
After upgrading to 3.2.2 from 3.0.8 I noticed that Bulk Update behaves
in a different way then it used to. Previously when one would search for
tickets and limit the search results by 10 per page, then could click
bulkupdate link (Update All These Tickets at Once) and see the page of
10 tickets to pick from. Currently a search limited to 10 tickets per
page will produce reulsts with 10 items per page, though after selecting
Bulk Update the page comes up with entire ticket list from the search -
i.e. one page with 300+ or as many tickets as it happend to find
according to criteria in the search. This same behavior is also present
in 3.3.10.
3.2.2 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.11
MySQL 4.0.17
3.3.10 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.12
Has anyone noticed similar behavior or am I alone here?
Sincerely,
Alex Rebrik.
P.S. For now to work-around this issue I’ve dropped some quick Java
script to “de-select” all tickets in BulkUpdate with one click (in our
case 300+ tickets usually turn up on a search with status=New /
ower=Nobody / queue=MainQueue) this isn’t the preferred way however.
Rt-devel mailing list
Rt-devel@lists.bestpractical.com
The rt-devel Archives
Apparently it wasn’t “always this way”. I just tested against RT 3.0.4
and RT 3.0.8 clean installs. RT 3.0.4 has SearchBuilder-0.92, RT 3.0.8
has p5-DBIx-SearchBuilder-0.96, both work as expected (by me) i.e. a
search limited to 10 items per page will feed those 10 items on the page
you’re looking at to Bulk Update. This functionality being absent in
newer versions make it a pretty serious bug IMHO, we for one rely on
this feature for our customer reps. to be able to grab more than one
ticket at a time efficiently.
–AlexOn Sat, 2004-10-30 at 07:16, Todd Chapman wrote:
I’m pretty sure it always worked that way…
On Fri, Oct 29, 2004 at 04:32:52PM -0700, Alex Rebrik wrote:
Greetings,
After upgrading to 3.2.2 from 3.0.8 I noticed that Bulk Update behaves
in a different way then it used to. Previously when one would search for
tickets and limit the search results by 10 per page, then could click
bulkupdate link (Update All These Tickets at Once) and see the page of
10 tickets to pick from. Currently a search limited to 10 tickets per
page will produce reulsts with 10 items per page, though after selecting
Bulk Update the page comes up with entire ticket list from the search -
i.e. one page with 300+ or as many tickets as it happend to find
according to criteria in the search. This same behavior is also present
in 3.3.10.
3.2.2 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.11
MySQL 4.0.17
3.3.10 Installation is:
perl 5.8.5
mod_perl 1.29
apache 1.3.33
DBIx-SearchBuilder 1.12
Has anyone noticed similar behavior or am I alone here?
Sincerely,
Alex Rebrik.
P.S. For now to work-around this issue I’ve dropped some quick Java
script to “de-select” all tickets in BulkUpdate with one click (in our
case 300+ tickets usually turn up on a search with status=New /
ower=Nobody / queue=MainQueue) this isn’t the preferred way however.
Rt-devel mailing list
Rt-devel@lists.bestpractical.com
The rt-devel Archives
!DSPAM:4183abf3308651872012089!