You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
If we are not eventually displaying the reorder action under events or not sending out notification for reordering, then may be we do not need to capture this in workitem revision table.
Thoughts?
The text was updated successfully, but these errors were encountered:
That could be a problem IMO. Because when you re-order one WI, you'd technically be affecting the order of many other workitems. So if we move one WI, all the affect WI's trail would reflect the re-order.
But if we would be displaying events for the entire product in future, 'Reordering' should display there as a singular action.
So lets say I'm changing the position of 5th WI in the list by dragging it to 1st position. This will change the position of next 4 WI one position lower. Would that move in the sequence not be registered as a change?
Also, I meant to talk about 'space' level notifications when I wrote 'product'. My bad!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We capture the reorder action in workitem revision table (https://github.com/fabric8-services/fabric8-wit/blob/master/workitem/workitem_repository.go#L562)
If we are not eventually displaying the reorder action under events or not sending out notification for reordering, then may be we do not need to capture this in workitem revision table.
Thoughts?
The text was updated successfully, but these errors were encountered: