[
https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360145#comment-15360145
]
Nicolas Malin commented on OFBIZ-7611:
--------------------------------------
Yes you right, you start just to add changeByUserLoginId field and I continue
the idea to define a EntityStatus concept manage by entity-auto and help
developer to respect it.
I think we can just change the issues name and get it all done in one fell
swoop ?
I can finish the entity improvement and we use subtask to add the missing field
like you already done, add the create service by entity-auto and propagate his
call
> Track userlogin for status change
> ---------------------------------
>
> Key: OFBIZ-7611
> URL: https://issues.apache.org/jira/browse/OFBIZ-7611
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Nameet Jain
> Assignee: Nicolas Malin
> Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch
>
>
> Currently in OFBiz, 'changedByUserLoginId' field is missing from status
> entities (like: ShipmentStatus). Using this field we can maintain the history
> for each status change made by user.
> Update all respective service and events to ensure this field gets updated.
> Here is the list of entities with missing this field.
> 1. BudgetStatus
> 2. ContactListCommStatus
> 3. CustRequestStatus
> 4. ExampleStatus
> 5. FinAccountStatus
> 6. InventoryItemStatus
> 7. InvoiceStatus
> 8. PartyStatus
> 9. RequirementStatus
> 10. ShipmentStatus
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
