March 16, 2012

Webinar Recording: Intro to Calculated Fields

Helix ALM
Events
Thank you to everyone who participated in the Intro to Calculated Fields webinar. The webinar recording is now available if you weren’t able to attend or if you would like to watch it again. Q&A from the session follows. Remember, this is the first in a three-part series. You can still register for the webinar series. http://youtu.be/1ghbj29grYg

Q & A

Q: Do calculated fields work for any item type in TestTrack, or only issues?­ A: Calculated fields are supported across all item types, including issues, test cases, test runs, and all requirement types. Q: What versions of TestTrack support calculated fields? A: Calculated fields were introduced in TestTrack 2012, released last month. Q: Can you use calculated fields with other fields to create a new calculated field? A: Yes, that’s the power of calculated fields. You can take information from other parts of an item and essentially create a whole new piece of data. For example, you could combine severity and location of an issue to define an issue’s priority. Q: Can we make a calculation based on the status of a different item? For example, the risk level of one item when it or another item changes? A: Not currently. Right now calculated fields don’t have the ability to look outside of the item, meaning they can’t pull data from linked items or use other criteria outside of their own scope. Q: Is all the functionality shown in the demonstration also available in the web version of TestTrack 2012? A: Yes, both the web and desktop clients have full support for creating, updating, and using calculated fields. Q: How do you set up the date/time calculations—like weeks to close? A: See Using Date Functions in Calculated Fields. Q: If you change the calculation and rerun a report will you get a different value? A: Reports use the field values in an item at the time the report is run. If the changed formula hasn't been recalculated when a report is run, the report won't show the new value because the field itself doesn't have the new value. Calculated fields are always recalculated when another field or event is changed on an item.