[MGNLPN-140] Refine and fix renaming action Created: 04/Jun/14 Updated: 05/Jun/14 Resolved: 05/Jun/14 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Personas App |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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
|
| Description |
|
I've noted in the Personalization module bundled with 5.3 beta 4, that we do have two issues with the renaming action.
On 1): I know we had that discussion with some of you on reworking all rename actions everywhere to only change the nodename, and that would eventually lead to the action being renamed to something like "rename node" or "rename XYZ node". But I'd like to keep all actions named consistently for now, so that we don't have a mixed approach - which means that we should still call it "rename persona" here. I'll create a separate issue to rework the "rename" actions everywhere. |