+1
I agree with Nick's assessment and would add that it's difficult to know how to update the downstream item without knowing the exact change that occurred in the upstream item. As currently implemented the "Suspect" flag tells us that
something has changed but doesn't give enough information so that we know
how to take action regarding the change.
I have investigated ways to work around this issue, and here's the only solution I've found.
1. Search the project Activity Stream for "suspect" and the item of interest.
2. Identify the relevant event and note the date.
3. Search the version history of the upstream item for versions around the date in the "suspect flag changed" event.
4. Repeat for every suspect flag
I'm guessing a Velocity report could gather this information using the EventLogDao and EventEntry but I haven't had time to finish implementing it.
------------------------------
Theresa
Fujifilm SonoSite
WA United States
------------------------------
Original Message:
Sent: 11-20-2018 03:39
From: Lien Bäcker
Subject: Find when Suspect was set to "True"
we also have the interest on this feature
------------------------------
Lien Bäcker
Gira, Giersiepen GmbH & Co. KG
Original Message:
Sent: 10-12-2018 08:58
From: rene wilsing
Subject: Find when Suspect was set to "True"
We would be interested in such feature too.
------------------------------
rene
Original Message:
Sent: 10-11-2018 07:12
From: Ekaterina Kessner
Subject: Find when Suspect was set to "True"
We would be interested in such feature too.
------------------------------
Ekaterina
Original Message:
Sent: 10-04-2018 14:46
From: Nick Hainline
Subject: Find when Suspect was set to "True"
It would be a nice feature to be able to see when a suspect link was created between items. Maybe users could inspect the Version history and see notes in there for exactly what change triggered it.
The problem is that there could be many changes that occurred in an item but finding the exact change that caused the suspect link to trigger could be buried and difficult to pinpoint.
Thanks!
Nick
------------------------------
Nick Hainline
NV
------------------------------