History Activity log to be moved when an Item is moved to another board

Feature requests
,
21

But then we lose the history from the other board that item had spent time on. I can’t believe this hasn’t been added to the list of items to work on. The history is still there, since it shows back up when you move the item back to that board, so why can’t it display in the history of the item no matter where that item moves to?

22

Isn’t there still an update on this? It is a must for us as well.

23

We’re also looking for this feature! Can we please get an update?

24

How does your automation to create an update with the log work?

25

I am also still in need of this functionality. Please keep the activity log attached to the item, when moving between boards.
We clutter our updates with changes and unnecessarily use up our automations as a workaround and noone is happy with that.

26

Hi Nils, I used an automation in a workflow where an item was being submitted for approval. It was formatted similar to "When STATUS changes to SOMETHING move ITEM to BOARD and create an update with THIS TEXT’ and then I selected the existing data elements so at least at the point of transfer I could retain what values the person had entered originally even after the item moved through multiple boards during processing. Best I could come up and was only useable under very limited conditions.

28

Thank you for the explanation!

So to clarify:
You could only “save” the latest state just prior to moving and not all the changes from creation to moving?

29

Correct. This automation only serves to capture current values at the time the item is moving to the new board so it’s usefulness is limited.

Matthew Buchmeier CPCU, AU
Business Process Consulting Specialist - IT
Office: 800.282.7648 | Cell 863.450.0635
summitholdings.com | Connect with Summit on LinkedIn!

1 Like
30

I Agree, it’s a huge problem.

31

Thank you for the option - unfortunately it doesn’t have the same historical information required. i.e. “Who” did “what” for tracking purposes, “what” automated triggered this action. This is critical information needed for an item. If duplicating an item can copy over the updates, why can’t moving an item retain the historical information?

1 Like
32

How do you mean reappear? What work around are you doing?