Issue #2271091 by eshta: Only listen for goals on campaigns that are currently running.
Issue #2275483 by eshta: Remove automatic option labelling when creating a runJS personalize element.
Issue #2266459 by craig.norris, eshta: Clarified instructions on personalize elements admin pages.
Issue #2274815 by craig.norris, eshta: Consistent naming for variation set names.
Issue #2266459 by eshta: Updated control value upon submit for personalize elements.
Issue #2274815 by eshta: Fixed add personalize elements link in test.
Issue #2275937 by eshta: Added sorting capabilities to agents and option sets loading.
Issue #2276255 by eshta: Allow empty content variations to be treated as non-options in personalize elements
Issue #2280559: Fix for broken querystring parameter context
Create automatic targeting interface to determine when visitor contexts show in campaign edit form.
Get all possible values for explicit targeting context options.
typo
Read all contexts for a campaign.
Explicit targeting dependent upon auto targeting
Allow fixed targeting values to be dependent or independent of campaign auto-targeting context.
Add limit indicator to context classes for getPossibleValues()
Refactored value select to handle limit clearly.  Also add context name into value data.
Add visitor context plugin name to context rules in order to facilitate loading of assets by fixed targeting context.
Fix styling for "add context" button.
Enable loading of context assets when context is only fixed targeting.