Good idea but I would have the action differently or at least additional: "Submit for Approval and Build for Staging". In my company no one will approve the rules in launch. They get approved indirectly while testing on the Staging environment.

We have introduced an issue with the latest release and I know exactly which rule is responsible. Now I want to check what was changed when, but with the audit log it is nearly impossible to find the changes. So I suggest a filter mechanism for all the headers:date (range for the filter)propertyuser...

Awesome idea, the same was implemented in the debugger extension for chrome, but there needs to be refreshed every time I use it and is still a bit annoying to use. But here it should be easy to integrate it, especially since you are already defining the Analytics Suite in the extension which could ...

I posted a similar idea here: Add an indicator if the "Set Variable" action contains custom code My idea was even one step higher in the rule overview, so you don't even have to open the action.

I mentioned this a few months back and it is already under review:Natural order of eVars, props and events

I actually have a similar problem with referencing in another project I am working on. I also didn't find the perfect solution yet, else I could share it here. But I like stewarts ideas and add my two cents:Why only discuss about conditions?Events: I think events don't really need to be shared withi...

Our security department doesn't trust anyhting hosted on the cloud, so we use the "Create archive" option for the environments to download a ZIP file which we then manually load into AEM DAM. This is cumbersone as it seems the folder name hashes change from time to time and the DAM transforms all fo...

There already is an idea with the same basic premisse: Reuse events, conditions, exceptions in rules

If your website already has such a library loaded in the window namespace, you can use it within the custom code as well. The only problem is that you would need to have the other library loaded before and also synchroniously.

Not sure if I understand you correclty, but in either Chrome or Firefox you can still pretty print the compressed file from launch. Just open the developert tools, navigate to the source, in your cause probably the launch-HASH-ENV-min.js and click the {} icon. There are still some limitations to deb...