Cloning Action Trigger can fail to clone environment and parameters

Bug #1891232 reported by Blake GH
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

EG 3.4
OpenSRF 3.2
PG 9.6

Evergreen suffers from a bug when cloning an action trigger definition. The interface asks the user if they would like to also clone the environment. When staff chose "yes", Evergreen doesn't always* clone the environment. It's unclear when/where/why it doesn't work because it does work sometimes. It seems that it fails more often than not though.

This bug was reported in 2011: bug 728055 with basically the same issue.

I propose that we clone the environment and parameters as a matter of course without the added choice. It's more clicking and I would venture that everyone generally wants to clone that stuff with the template (because it's probably broken without it).

There is a database function already written that does this. Not sure how long this link will work but here it is: https://pastebin.com/2hcK8Xjj

Code attached as well ( clone_action_trigger_event_def_for_org.sql )

Revision history for this message
Blake GH (bmagic) wrote :
description: updated
Blake GH (bmagic)
summary: - Cloning Action Triggers fails to clone environment and parameters
+ Cloning Action Trigger can fail to clone environment and parameters
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.