[MGNLDAM-539] Rename asset behaviour is confusing Created: 29/Jan/15 Updated: 01/Jul/15 Resolved: 06/Apr/15 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | DAM App |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | 2.0.9 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Frank Sommer | Assignee: | Trang Truong |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support, ux | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d | ||
| Original Estimate: | 0.25d | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
If you wan't to rename a asset the node of the asset will be renamed. The editor does not see the change, except he looks at the node path in the status bar. In the tree nothing is changed. |
| Comments |
| Comment by Trang Truong [ 03/Apr/15 ] |
|
As I know we had a long discussion on this, we still want to keep filename when we take action rename asset, so the solution is add 2 fields for renaming asset-name, node name and change action name to "Rename node". |
| Comment by Eric Hechinger [ 07/Apr/15 ] |
|
Please create in version handler a Otherwise a user that has a 2.0.8 version will never be updated with your changes. Same for your test class. and do not create the fields that are supposed to be created before running the update task
// Node fields = NodeUtil.createPath(session.getRootNode(), "/modules/dam-app/dialogs/renameAsset/form/tabs/item/fields", NodeTypes.ContentNode.NAME);
// fields.addNode("assertName", NodeTypes.ContentNode.NAME);
// fields.addNode("jcrName", NodeTypes.ContentNode.NAME);
|