2.0 - unable to clone action trigger event definitions
Bug #728055 reported by
Ben Shum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen version: 2.0.1
OpenSRF version: 1.6.2
PostgreSQL version: 8.4
Linux distribution: Ubuntu Lucid 10.04
When using the notifications / action triggers interface and attempting to clone an existing event definition into a new one, we seem to be losing certain pieces of information along the way. The hook, reactor, and validator fields are "cloned" empty and filling these in with the original entries doesn't result in a successful cloning (it appears that the environment and parameters do not copy successfully either).
Checking our syslog entries, we have not seen any indication of the source of this problem, but will continue experimenting.
Changed in evergreen: | |
milestone: | none → 2.0.3 |
Changed in evergreen: | |
status: | Confirmed → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Changed in evergreen: | |
assignee: | Lebbeous Fogle-Weekley (lebbeous) → nobody |
To post a comment you must log in.
One other common issue I'm seeing (regardless of having the various hook, reactor, validator fields copied) during cloning is that the field to enter granularity is not shown at all. The label is there, but the actual field for entry is not.
I tested this behavior on a fresh install of Evergreen 2.0 with a clean DB and the stock A/T event definitions. I was unable to consistently clone triggers with that either; though I did notice that I was able to clone A/T events with a validator set of "NOOP_True". Any other one of the defaults A/Ts I chose failed, such as with validator "CircIsOverdue" or "HoldIsAvailable".
Will continue with additional testing...