Actions
Bug #3131
closed
Manage files and folders Technique has improper reporting when dealing with non existent file we don't wish to create
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When trying to manage a non existant file, and set the action on file or folder to "do nothing", the reporting is broken, as we have two success from the File component of the technique
2013-01-02 18:31 result_success test 3005 QA3005 File /tmp/test3005 No action on /tmp/test3005 2013-01-02 18:31 result_success test 3005 QA3005 File /tmp/test3005 The element /tmp/test3005 was not set to be created
The configuration of the directive is shown in the attached file
Observed on 2.4, but I believe it applies to 2.3
Files
Updated by Matthieu CERDA almost 12 years ago
- Status changed from New to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:c8c78ecd259253384aea8554d9f454147444549b.
Updated by Nicolas PERRON almost 12 years ago
Applied in changeset commit:65e8b1f103f78a1752fbd58ca31ce2e53a2f0bf8.
Updated by Nicolas PERRON almost 12 years ago
Applied in changeset commit:b80c6f1e8fb262fcd10223b1c46727ca60c2bb12.
Updated by Jonathan CLARKE almost 12 years ago
- Project changed from Rudder to 24
- Category deleted (
Techniques)
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Actions