[RECOMMEND-3] Scoring trait selection fields break for personas Created: 28/Jun/19 Updated: 30/Sep/20 Resolved: 30/Sep/20 |
|
| Status: | Closed |
| Project: | Content Recommender |
| Component/s: | None |
| Affects Version/s: | 1.0.4, 1.0.8 |
| Fix Version/s: | 1.0.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jeffrey van der Heide | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | personalization, personalization-integration, recommender | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3h | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 5.7.3 |
||
| 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
|
| Date of First Response: |
| Description |
|
I understand this is an incubator project, but just wanted to share these findings. After saving and re-opening the persona the trait fields will have combined in to both fields, saving again will break the field further and you can no longer enter the correct information as both fields will automatically change to the last changed one. Right now it's just one scoring model, but if there were multiple there's quite a lot of work involved to restore the persona's to working order. e.g. the following screenshot, was `/Senior` and `500`, editing the score model to show `/Senior` will change the threshold to `/Senior` and changing the threshold to `500` will change the model to `500` etc.
|
| Comments |
| Comment by Teresa Miyar [ 16/Jun/20 ] |
|
This issue has been fixed for version 1.0.9 compatible with Magnolia 6.1 |