I know I must be missing something obvious hear, but I can’t find the
answer. I’ve had complaints about updates not displaying for a ticket.
The email would go out, but the reply was not shown in the Ticket
History. I looked into it and saw the data was there just not
displaying on the web page. So I set the $OldestTransactionsFirst
to ‘0’ and the data showed up to the top of the history. This turned
to be an option the users wanted anyways. My question is how do you
access the history data that is not showing on the page?
Thanks.
Scott T. Hildreth shildreth@allantgroup.com
Scott,
Normally, I would say that giving the privilege "ShowOutgoingEmail"
would do the trick. It works just like “ShowTicketComments”. Having
rights like “SeeQueue” and “ShowTicket” does not do the trick alone.
However, I am now a little confused hearing that flipping the switch on
$OldestTransactionsFirst did the trick. Unless you had already granted
that privilege (“ShowOutgoingEmail”) and the descending order was the
problem. Interesting.
Kenn
LBNL
Scott T. Hildreth wrote:
Scott,
Normally, I would say that giving the privilege “ShowOutgoingEmail”
would do the trick. It works just like “ShowTicketComments”. Having
rights like “SeeQueue” and “ShowTicket” does not do the trick alone.
However, I am now a little confused hearing that flipping the switch on
$OldestTransactionsFirst did the trick.
Maybe, I didn’t explain it right. They can see the replies & email it
is that all the history does not display on the page. By reversing the
order the newer transactions fill the page now and the older history is
not displaying. I’m wondering if this is some sort of limit set?
Unless you had already granted
that privilege (“ShowOutgoingEmail”) and the descending order was the
problem. Interesting.
Kenn
LBNL
Scott T. Hildreth wrote:
I know I must be missing something obvious hear, but I can’t find the
answer. I’ve had complaints about updates not displaying for a ticket.
The email would go out, but the reply was not shown in the Ticket
History. I looked into it and saw the data was there just not
displaying on the web page. So I set the $OldestTransactionsFirst
to ‘0’ and the data showed up to the top of the history. This turned
to be an option the users wanted anyways. My question is how do you
access the history data that is not showing on the page?
Thanks.
Scott T. Hildreth shildreth@allantgroup.com
Scott,
Normally, I would say that giving the privilege "ShowOutgoingEmail"
would do the trick. It works just like “ShowTicketComments”. Having
rights like “SeeQueue” and “ShowTicket” does not do the trick alone.
However, I am now a little confused hearing that flipping the switch on
$OldestTransactionsFirst did the trick.
Maybe, I didn’t explain it right. They can see the replies & email it
is that all the history does not display on the page. By reversing the
order the newer transactions fill the page now and the older history is
not displaying. I’m wondering if this is some sort of limit set?
This ticket I am looking at has 83 transactions. Only 17 or so show
up in the History section of the page. Is there a way to display all
the transactions or have “next page” link? Does anyone else have
this issue?
Unless you had already granted
that privilege (“ShowOutgoingEmail”) and the descending order was the
problem. Interesting.
Kenn
LBNL
Scott T. Hildreth wrote:
I know I must be missing something obvious hear, but I can’t find the
answer. I’ve had complaints about updates not displaying for a ticket.
The email would go out, but the reply was not shown in the Ticket
History. I looked into it and saw the data was there just not
displaying on the web page. So I set the $OldestTransactionsFirst
to ‘0’ and the data showed up to the top of the history. This turned
to be an option the users wanted anyways. My question is how do you
access the history data that is not showing on the page?
Thanks.
Scott T. Hildreth shildret@scotth.emsphone.com
Scott,
Normally, I would say that giving the privilege "ShowOutgoingEmail"
would do the trick. It works just like “ShowTicketComments”. Having
rights like “SeeQueue” and “ShowTicket” does not do the trick alone.
However, I am now a little confused hearing that flipping the switch on
$OldestTransactionsFirst did the trick.
Maybe, I didn’t explain it right. They can see the replies & email it
is that all the history does not display on the page. By reversing the
order the newer transactions fill the page now and the older history is
not displaying. I’m wondering if this is some sort of limit set?
This ticket I am looking at has 83 transactions. Only 17 or so show
up in the History section of the page.
Well, I opened my eyes wider and found this,
http://wiki.bestpractical.com/view/HideTransactions
which should show all the history on the History Tab,
although it shows a couple of more of the Transactions,
they are all not there.
Something is limiting the page size, not sure what. I will
continue testing, just seeing if more info will spark an
answer.
Is there a way to display all
the transactions or have “next page” link?
I see this is on the WishList on the wiki,
"Ability to display ticket history by page, e.g. 15 rows/transaction
logs per page, with Next, First, Previous, Last buttons/links at the
bottom or top. Especially helpful and useful for tickets with huge
history/transactions and if using RT from a slow connection.
Does anyone else have
this issue?
Thanks for listening. :-)
Unless you had already granted
that privilege (“ShowOutgoingEmail”) and the descending order was the
problem. Interesting.
Kenn
LBNL
Scott T. Hildreth wrote:
I know I must be missing something obvious hear, but I can’t find the
answer. I’ve had complaints about updates not displaying for a ticket.
The email would go out, but the reply was not shown in the Ticket
History. I looked into it and saw the data was there just not
displaying on the web page. So I set the $OldestTransactionsFirst
to ‘0’ and the data showed up to the top of the history. This turned
to be an option the users wanted anyways. My question is how do you
access the history data that is not showing on the page?
Thanks.
Scott T. Hildreth shildreth@allantgroup.com
Scott,
Normally, I would say that giving the privilege "ShowOutgoingEmail"
would do the trick. It works just like “ShowTicketComments”. Having
rights like “SeeQueue” and “ShowTicket” does not do the trick alone.
However, I am now a little confused hearing that flipping the switch on
$OldestTransactionsFirst did the trick.
Maybe, I didn’t explain it right. They can see the replies & email it
is that all the history does not display on the page. By reversing the
order the newer transactions fill the page now and the older history is
not displaying. I’m wondering if this is some sort of limit set?
This ticket I am looking at has 83 transactions.
If I query the Transactions table, selecting only transactions for this
ticket that were created by non-RT::System ids, there are 29. All of type
RT::Ticket. If unset the $OldestTransactionsFirst, the history on the display
page shows the first 20 Tickets (non-system tickets, I added the HideTransactons override)
If re-set $OldestTransactionsFirst in RT_SiteConfig.pm, stop apache, remove
mason_data/obj/*, restart apache, search for that ticket, the ticket display
only shows the last 7 tickets. I have looked at RT code and read relevant chapters
in RT Essentials and I cannot figure out why the all history will not show up
in the History section. I feel like I am really overlooking something obvious,
does anyone have any ideas on what is going?
Thanks.
Only 17 or so show
up in the History section of the page.
Well, I opened my eyes wider and found this,
http://wiki.bestpractical.com/view/HideTransactions
which should show all the history on the History Tab,
although it shows a couple of more of the Transactions,
they are all not there.
Something is limiting the page size, not sure what. I will
continue testing, just seeing if more info will spark an
answer.
Is there a way to display all
the transactions or have “next page” link?
I see this is on the WishList on the wiki,
"Ability to display ticket history by page, e.g. 15 rows/transaction
logs per page, with Next, First, Previous, Last buttons/links at the
bottom or top. Especially helpful and useful for tickets with huge
history/transactions and if using RT from a slow connection.
Does anyone else have
this issue?
Thanks for listening. :-)
Unless you had already granted
that privilege (“ShowOutgoingEmail”) and the descending order was the
problem. Interesting.
Kenn
LBNL
Scott T. Hildreth wrote:
I know I must be missing something obvious hear, but I can’t find the
answer. I’ve had complaints about updates not displaying for a ticket.
The email would go out, but the reply was not shown in the Ticket
History. I looked into it and saw the data was there just not
displaying on the web page. So I set the $OldestTransactionsFirst
to ‘0’ and the data showed up to the top of the history. This turned
to be an option the users wanted anyways. My question is how do you
access the history data that is not showing on the page?
Thanks.
Scott T. Hildreth shildreth@allantgroup.com
If I query the Transactions table, selecting only transactions for this
ticket that were created by non-RT::System ids, there are 29. All of type
RT::Ticket. If unset the $OldestTransactionsFirst, the history on the display
page shows the first 20 Tickets (non-system tickets, I added the HideTransactons override)
If re-set $OldestTransactionsFirst in RT_SiteConfig.pm, stop apache, remove
mason_data/obj/*, restart apache, search for that ticket, the ticket display
only shows the last 7 tickets. I have looked at RT code and read relevant chapters
in RT Essentials and I cannot figure out why the all history will not show up
in the History section. I feel like I am really overlooking something obvious,
does anyone have any ideas on what is going?
I just looked at the 3.6.3 code, and I can’t see anything that would
limit the number of history records shown, nor do I see anything
different with OldestTransactionsFirst aside from ASC vs. DESC in the
select. What code base are you on?
Regards,
joe
Joe Casadonte
joe.casadonte@oracle.com
========== ==========
== The statements and opinions expressed here are my own and do not ==
== necessarily represent those of Oracle Corporation. ==
========== ==========
If I query the Transactions table, selecting only transactions for this
ticket that were created by non-RT::System ids, there are 29. All of type
RT::Ticket. If unset the $OldestTransactionsFirst, the history on the display
page shows the first 20 Tickets (non-system tickets, I added the HideTransactons override)
If re-set $OldestTransactionsFirst in RT_SiteConfig.pm, stop apache, remove
mason_data/obj/*, restart apache, search for that ticket, the ticket display
only shows the last 7 tickets. I have looked at RT code and read relevant chapters
in RT Essentials and I cannot figure out why the all history will not show up
in the History section. I feel like I am really overlooking something obvious,
does anyone have any ideas on what is going?
I just looked at the 3.6.3 code, and I can’t see anything that would
limit the number of history records shown, nor do I see anything
different with OldestTransactionsFirst aside from ASC vs. DESC in the
select.
I couldn’t find anything either.
What code base are you on?
3.6.4, but it happens with 3.6.3 as well.
Scott T. Hildreth shildreth@allantgroup.com