uto ticket reply.
4. Assigning tickets / transferring to someone else (when not logged in
as root)
5. 3rd Party CRM integration basics.
Thanks in advance to all the folks here, specially the creators of RT.
Best,
Reza.
-
RT 4.4 and RTIR training sessions, and a new workshop d
could
connect to easily.
Thank you!
Reza.
Alex Hall wrote on 10/24/2016 5:16 PM:
Customizing email notifications as in #3 is done through the
templates. As root, or a super user, go to Admin > Templates > Select.
There you'll find a table with all the templates the system u
ot;Request Tracker for
Beginners" guide till I pass out.
Thanks for welcoming me to the community.
Cheers!
Reza.
On Mon, 24 Oct 2016 at 21:50 Reza <mailto:reza.toro...@gmail.com>> wrote:
Greetings Folks:
I successfully installed RT on a virtual machine and it has be
lmost ALL ticketing systems I have seen,
have a random arbitrary numeric or alpha-numeric ID. Any other
suggestions on how to approach not displaying an obvious number to end
users?
Thanks!
Reza.
Jeffrey Pilant wrote on 10/25/2016 10:12 AM:
Reza writes:
The last 24-48 hrs has been an am
ecide to simply call for
support.
Thoughts, ideas and suggestions welcome.
Best,
Reza.
Jeffrey Pilant wrote on 10/25/2016 2:43 PM:
Reza writes:
The use case for random IDs is quite simple. Ascending / serial number
of IDs compromises confidentiality. End users would be able to guess
how b
RT via the REST API?
Thanks!
Reza.
[Superbly pumped to learn more. Cheers!]
-
RT 4.4 and RTIR training sessions, and a new workshop day!
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017
g all
the steps and questions that I'm coming up with. Perhaps that doc will
help with future learning of enthusiasts.
Hopefully more people will share what they are doing with the REST API,
as it gives us all more perspective of what can be done and what people
doing in real life.
ssarily the best
business practice.
I like to keep things well organized and have separate groups for
different unique permissions.
In theory your concept may work, but not advisable in my opinion, coming
from a security perspective, in the name of keep things organized and
secure.
Cheer
is
important to see the total resolved versus having to go to the search
field.
If anyone could guide me to the proper direction, it would be appreciated.
Thank you,
Reza.
-
RT 4.4 and RTIR training sessions, and a new workshop day!
https://bestpractical.com/training
* Los Angeles - Q1 2017
interested, please reply to this post and I will try to work
on getting a conference line free of charge, or perhaps have a group
chat / talk on Skype or other chat mediums.
Thanks in advance!
Reza.
-
RT 4.4 and RTIR training sessions, and a new workshop day!
https://bestpractical.com
rence type
setting and with the spirit of group study, we can definitely find a
solution.
So far the list is:
1. Alex (United States)
2. Myself (Canada)
3. Bengan (Sweden)
4. Vinzenz (Germany - can we included you in as well?)
5. ... List yourself here, if you are interested. Thanks!
Th
ot;Incident
Reports" queue. The "deny" option takes precedence over "allow" option
per my experience, so it is also possible that one of your groups under
"User Groups", under your "Incident Reports" queue does not have
permission to create tickets.
here per this anomaly.
Cheers!
Reza.
Stephen Switzer wrote on 11/22/2016 3:37 PM:
Reza,
I think you may have misinterpreted my screenshot. "Everyone",
"Privileged", "Unprivileged", "Owner", etc are all "highlighted" just
to show that there
13 matches
Mail list logo