When I use bulk update to change ticket watchers, my open
tickets are set to new, even though I have left the
’Make Status’ dropdown set to ‘-’.
-Todd
When I use bulk update to change ticket watchers, my open
tickets are set to new, even though I have left the
’Make Status’ dropdown set to ‘-’.
-Todd
When I use bulk update to change ticket watchers, my open
tickets are set to new, even though I have left the
‘Make Status’ dropdown set to ‘-’.
I have the same trouble. My closed tickets are set to ‘Rejected’
Nicolas
In Web.pm sub ProcessTicketBasics, why is this line important?
$ARGSRef->{‘Status’} ||= $TicketObj->Status;
Why update the status if it wasn’t selected in the Bulk.html form?
-ToddOn Fri, Oct 08, 2004 at 04:28:34PM +0100, nvarney@edt.fr wrote:
When I use bulk update to change ticket watchers, my open
tickets are set to new, even though I have left the
‘Make Status’ dropdown set to ‘-’.I have the same trouble. My closed tickets are set to ‘Rejected’
Nicolas
Be sure to check out the RT wiki at http://wiki.bestpractical.com
What happens is, whichever ticket is processed first
in the bulk update, all other tickets get the first
ticket’s status.
-ToddOn Fri, Oct 08, 2004 at 10:10:05AM -0400, Todd Chapman wrote:
In Web.pm sub ProcessTicketBasics, why is this line important?
$ARGSRef->{‘Status’} ||= $TicketObj->Status;
Why update the status if it wasn’t selected in the Bulk.html form?
-Todd
On Fri, Oct 08, 2004 at 04:28:34PM +0100, nvarney@edt.fr wrote:
When I use bulk update to change ticket watchers, my open
tickets are set to new, even though I have left the
‘Make Status’ dropdown set to ‘-’.I have the same trouble. My closed tickets are set to ‘Rejected’
Nicolas
Be sure to check out the RT wiki at http://wiki.bestpractical.com
Be sure to check out the RT wiki at http://wiki.bestpractical.com