Re: (ris) ticketing systems

Hi Arife,
replacemnt of ris@ripe.net is activated. it's called ris-int@ripe.net. we can start to use this new list for internal communications.
ris@ripe.net would be received by us until the begining of July.
I'm not quite sure if I understand. We should start using ris-int@r.n, but everybody currently on ris@r.n, should be on the ticket queue and get those mails until he/she decides to unsubscribe.
You're right! It's not still clear for me how xrtt works. When we have progress on RIS ticket system, I will check out those things with you guys before making a big change.
FYI: My wishlist for RIS (and if/when it moves to xrtt, OPS) ticketing system is to be able to check the status and all correspondence on a particular ticket, regardless of receiving yes or all e-mail coming in to the queue. For the *current* ops ticketing system one can see the status via the iii pages, or by doing a "req -show <ticketno>" on the command line (and "reqq" shows open ticket queue) I don't know xrtt, but similar functionality would be quite nice. -- Rene

My wishlist for RIS (and if/when it moves to xrtt, OPS) ticketing system is to be able to check the status and all correspondence on a particular ticket, regardless of receiving yes or all e-mail coming in to the queue.
This is the funtionality I expect to see as well. I have already sent a request to SED to allow people (who are in ris list) to use xrtt. When they enable it, I assume you would be able see all RIS related tickets.
For the *current* ops ticketing system one can see the status via the iii pages, or by doing a "req -show <ticketno>" on the command line (and "reqq" shows open ticket queue)
I don't know xrtt, but similar functionality would be quite nice.
Me neither. In SED, I guess only Timur looks like the guru of xrtt. Arife
participants (2)
-
Arife Vural
-
Rene Wilhelm