Product Idea

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
------------------------------

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
------------------------------

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
------------------------------

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
------------------------------

+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
------------------------------

+1
we are also interested.

------------------------------
Alessandro
Systems Engineer
SICK AG
------------------------------

Original Message:
Sent: 12-04-2019 13:29
From: Theresa Soares
Subject: Find when Suspect was set to "True"

+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
------------------------------

Adding this use case from a Support thread:

Our use case is that our tester have testscripts/testcases linked to system requirements.
If somebody changes the system requirement, the tester must check if his script is still valid, so he/she must know what change of the upstream item caused the suspect.
Right now the only thing I see is that a relationship IS suspect, not when. So it is possible that it was set 1 day ago or half a year ago.​

------------------------------
Sebastian
Requirements Engineer
Sick AG
------------------------------

------------------------------
Chloe Elliott
Jama Software
Portland OR
------------------------------

Original Message:
Sent: 12-05-2019 02:37
From: Alessandro Valli
Subject: Find when Suspect was set to "True"

+1
we are also interested.

------------------------------
Alessandro
Systems Engineer
SICK AG

Original Message:
Sent: 12-04-2019 13:29
From: Theresa Soares
Subject: Find when Suspect was set to "True"

+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
------------------------------

linking the full support thread:
https://community.jamasoftware.com/communities/community-home/digestviewer/viewthread?MessageKey=efef698b-5c76-4b62-ba3d-26379fdaaa1c&CommunityKey=c9d20d4c-5bb6-4f19-92eb-e7cee0942d51&tab=digestviewer#bmefef698b-5c76-4b62-ba3d-26379fdaaa1c

------------------------------
Chloe Elliott
Jama Software
Portland OR
------------------------------

Original Message:
Sent: 12-05-2019 12:37
From: Chloe Elliott
Subject: Find when Suspect was set to "True"

Adding this use case from a Support thread:

Our use case is that our tester have testscripts/testcases linked to system requirements.
If somebody changes the system requirement, the tester must check if his script is still valid, so he/she must know what change of the upstream item caused the suspect.
Right now the only thing I see is that a relationship IS suspect, not when. So it is possible that it was set 1 day ago or half a year ago.​

------------------------------
Sebastian
Requirements Engineer
Sick AG
------------------------------

------------------------------
Chloe Elliott
Jama Software
Portland OR

Original Message:
Sent: 12-05-2019 02:37
From: Alessandro Valli
Subject: Find when Suspect was set to "True"

+1
we are also interested.

------------------------------
Alessandro
Systems Engineer
SICK AG

Original Message:
Sent: 12-04-2019 13:29
From: Theresa Soares
Subject: Find when Suspect was set to "True"

+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
------------------------------