topic Re: Test Runs, Notifications, Computed Fields in Codebeamer

Test Runs, Notifications, Computed Fields

rattmice — Thu, 11 Jul 2024 16:42:43 GMT

We have a problem with having a notification sent from a Test Run when the item is transitioned to the Finished state. Our Test Run tracker has 2 custom Members fields: Lab Manager and Test Engineer. It also has the Assigned To field which is a computed field that is assigned its value based on the state of the item. If the state is Finished then it gets set to the Lab Manager field value, otherwise it is set to the Test Engineer value.

When a Test Run is created (and is not in the Finished state) the Assigned To is set to the Test Engineer field and that user will get a notification of the Test Run which is desired. However, when the Test Run is marked as Finished, the Assigned To field does get the value of the Lab Manager but that user does not get a notification that it is complete.

Because the Test Run's workflow is not editable we don't have the ability to add a workflow action (custom via groovy or any of the other built-in actions).

I tried manually subscribing the Lab Manager user for events to the Finished state but that does not trigger a notification during the transition but it will if I update the item while it is already in that state.

I have yet to look at the Velocity templates but that is my next option.

Anyone have a workaround to getting notifications sent when the Assigned To changes on a Test Run?

Re: Test Runs, Notifications, Computed Fields

EvaBertalan — Wed, 26 Feb 2025 10:10:35 GMT

Hi @rattmice ,

First it worth to check who was the user executing the state transition.

The users don't get notification about their own activities in Codebeamer.

If the user is the same as the one in Lab Manager field, then this behavior is expected.

Re: Test Runs, Notifications, Computed Fields

Alexej_L — Thu, 13 Mar 2025 09:15:52 GMT

Hi @rattmice ,

We encountered a similar issue in our use case where workflow actions are disabled for Test Runs (no Groovy scripting). As a workaround, we implemented Java-based listeners: the WorkflowListener (using the transitionTaken method) and the TrackerItemListener (using the trackerItemCreated and trackerItemUpdated methods). You can find more details here:

https://support.ptc.com/help/codebeamer/r2.2/en/index.html#page/codebeamer/developers_guide/4420193.html#

Perhaps this approach could also work for your use case.