Is it possibe to deactivate the user nobody without any Disadvantages for
the whole system?
or is it a recipe for an proximate event?
best regards john
You will need to run through all the scrips and perl code to
ensure that nothing sets the owner to Nobody and uses an actual
value. It sounds like a recipe for disaster with tickets being
assigned at creation to owners that cannot resolve them. It
may be that your workflow will allow that to work. What are
you trying to gain from this change?
Is it possibe to deactivate the user nobody without any Disadvantages for
the whole system?
or is it a recipe for an proximate event?
best regards john
You will need to run through all the scrips and perl code to
ensure that nothing sets the owner to Nobody and uses an actual
value. It sounds like a recipe for disaster with tickets being
assigned at creation to owners that cannot resolve them. It
may be that your workflow will allow that to work. What are
you trying to gain from this change?
To echo Ken, that’d be a lot of work.
What are you trying to do?
User “nobody” been there for ages and only purpose of this user is to
be Owner of tickets that are no owned by a real person. And it’s only
way RT core uses this user record.On Fri, Mar 4, 2011 at 10:47 AM, john s. fireskyer@gmx.de wrote:
What are you trying to gain from this change?
Nobody should use the nobodyuser to declarate the ticket created by nobody