# 2.4.0~alpha5 2012-02-17 * User story #741: Filter the list of Configuration Rules * User story #856: Make promises in order to assure that Rudder services are still running * User story #1752: make selectable items more visible, for example in the "Configuration rule settings" screen * Architecture #2012: The historization of the group doesn't store if the group is static or dynamic * User story #2051: Make selected item in tree more visible * Bug #2082: The librairy and core-lib in the Common PT have some copy_from bodies which don't use the proper port * User story #2107: Archiving objects in the web interface (import/export) should be logged in Event Logs * Architecture #2133: some pics deleted were used. the new path to pics need to be added in pics path * Bug #2134: Node name in popup for applicable policies (new node) says "No server found" * Architecture #2143: Historize human readable name of PT * Architecture #2198: Create events for all type of action stil lnot historized * Bug #2199: Git commit error on auto-archive should be a system error in log, not a user one * User story #2219: Allow changing the number of rows displayed for Configuration Rule lists * User story #2222: PT distributePolicy: Check status of webapp and endpoint, and restart jetty if several continuous tests fail * Bug #2223: The default group query is incomplete * User story #2231: Display component and key columns in node pt system log * User story #2233: PT distributePolicy: Check status of webapp and endpoint, and restart jetty if several continuous tests fail using the REST API * Bug #2238: Error message when deleting a Configuration Rule * Bug #2239: On the group screen, when clicking on a node name, the popup with the node details appears with error * User story #2240: Add a filter on the PI screen to search for a given PI * Bug #2241: rudder.rest.allowNonAuthenticatedUser attribute is not set after an upgrade on Debian system * Bug #2243: Missing event in modification going to be deployed * Bug #2244: Date of PT/PI/CR/Group archives is not valid * User story #2246: Allow to restore archive from HEAD * Architecture #2251: Packaging: use a variable to define which maven settings files to use * User story #2253: Automatically update the SQL schema on upgrade from to 2.4 (extra column in policyInstances and groups tables) * Bug #2256: Error "Something unexpected happened while serving the page at /secure/administration/archiveManagement" * Bug #2257: Successful Deployment event log is displayed as "Unknow event type" * Bug #2259: The date on Rudder's internal commits is messed up * Bug #2260: While trying to delete a PI, you get a frightening error message and a deleted but uncommited XML file in the GIT repository * Bug #2261: While trying to make a complete archive on the webapp for an export, a wild stacktrace appears * Bug #2262: The rudder-init script outputs a weird error at the "Add sample data" stage * Bug #2265: During an import of a rudder configuration-repository copy (from another root server), if you try to tag the archive without an annotation, JGit fails * Bug #2266: While importing a full archive from another root server, all the PI/PTs and CRs are here but no groups * Bug #2271: Import error with Rudder-core -> reportsInfo.sql * Architecture #2276: We don't need no more rudder-policy-templates exception in rudder-webapp dependencies * Architecture #2287: Change URL for uploading rudder artefacts * Architecture #2290: Remove deprecated scripts * User story #2292: Unclear error message when the policy-template library is not found or initialized in Git