[MGNLACTIVATION-153] Wrong mgnl:lastActivatedBy on assets created by copy or duplicate Created: 19/May/17  Updated: 15/Mar/21  Resolved: 15/Mar/21

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.5.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   
  • Login "eric"
  • Duplicate an asset in Assets app
  • Check mgnl:lastActivatedBy of the new asset
    -> Expected: "superuser" (original value)
    -> Actual: "eric" (although you didn't publish it)


 Comments   
Comment by Jan Haderka [ 15/Mar/21 ]

Activation module have been superseded by publishing module.

Generated at Sun Feb 11 23:00:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.