frozen requirements update in DB

[gmartinez]

At the level of DB in Testlink, a requirement when it freezes, how that information is updated tables? I've been reviewing Requirements tables, req versions and I find no evidence to determine whether the requirement has been frozen or not.

Thank you.

[TurboPT]

The field is named is_open. This appears in both the req_revisions and req_versions tables.

I used grep to search for 'frozen' in the requirements area:

Code: Select all

$ grep -rn '[Ff]rozen' lib/requirements/
//...
lib/requirements/reqOverview.php:128:            * 4. frozen (is_open attribute)
lib/requirements/reqOverview.php:172:                   // is it frozen?
lib/requirements/reqOverview.php:235:            * 4. frozen
//...

Just dig into that area to follow the handling. Searching from a higher directory will give more results for frozen, as it is used in variables and/or the template areas too.

HTH

[gmartinez]

Ok. What I see is that when you freeze a requirement, the only record in DB is the creation date and modification of the version. Can you confirm that this is true and there is no way to know at what date a requirement is frozen?

Thank you.

[TurboPT]

... Can you confirm that this is true and there is no way to know at what date a requirement is frozen?

I have not followed the handling, but I would think that if the modified date is set when the requirement is frozen, would that not be the reference date? Again, I would need to check/follow the handling, but that's how it seems to be. I'll post again once I have a chance to investigate, unless you discover something before I do.