On 2/3/2012 10:36 AM, Ronald J. Yacketta wrote:
Hello all!
We went live with rt 4.0.04 last night and have been getting reports
of end-users being unable to change ticket status in ANY queue from
New - Open.
Ticket 39927: Status 'open' isn't a valid status for tickets in this
queue.
We
On 2/3/2012 11:37 AM, Ronald J. Yacketta wrote:
On 2/3/2012 10:36 AM, Ronald J. Yacketta wrote:
Hello all!
We went live with rt 4.0.04 last night and have been getting reports
of end-users being unable to change ticket status in ANY queue from
New - Open.
Ticket 39927: Status 'open' isn't
On Fri, Feb 03, 2012 at 10:36:07AM -0500, Ronald J. Yacketta wrote:
Hello all!
We went live with rt 4.0.04 last night and have been getting reports of
end-users being unable
to change ticket status in ANY queue from New - Open.
Ticket 39927: Status 'open' isn't a valid status
On Fri, Feb 03, 2012 at 10:36:07AM -0500, Ronald J. Yacketta wrote:
Hello all!
We went live with rt 4.0.04 last night and have been getting reports
of end-users being unable
to change ticket status in ANY queue from New - Open.
Ticket 39927: Status 'open' isn't a valid status
On Fri, Feb 03, 2012 at 12:42:47PM -0500, Ronald J Yacketta wrote:
On Fri, Feb 03, 2012 at 10:36:07AM -0500, Ronald J. Yacketta wrote:
Hello all!
We went live with rt 4.0.04 last night and have been getting reports
of end-users being unable
to change ticket status in ANY
You really want all local configs in RT_SiteConfig.pm, not
RT_Config.pm. Next time you upgrade, any changes to RT_Config.pm will
be blown away.
Why doesn't Best Practical just do away this idea?
1. make install
put new RT_Config.pm in place
make a new 'RT_SiteConfig' help document
On Fri, Feb 03, 2012 at 01:34:52PM -0500, Jeff Blaine wrote:
You really want all local configs in RT_SiteConfig.pm, not
RT_Config.pm. Next time you upgrade, any changes to RT_Config.pm will
be blown away.
Why doesn't Best Practical just do away this idea?
1. make install
put new
Because having an RT_SiteConfig.pm that is the same as RT_Config.pm
means that RT can never tell you if you overrode the setting.
Sure it can. In those rare needs, the code can just compare
the value in RT_Config.pm to the one in RT_SiteConfig.pm.
If they're the same, it was not overridden.
On Fri, Feb 03, 2012 at 02:21:22PM -0500, Jeff Blaine wrote:
Because having an RT_SiteConfig.pm that is the same as RT_Config.pm
means that RT can never tell you if you overrode the setting.
Sure it can. In those rare needs, the code can just compare
the value in RT_Config.pm to the one in
