Last Update Date / Showing When Irrelevant Changes Happen

There are a few items that cause the last update date to be changes that I believe are irrelevant to the users. These few items may be important in the log, but not enough to change the 'last update date'.

Examples:
Name Changes
Change of State (locked/unlocked)

0
4 comments
Avatar
Joseph Hamdan

Hi Zach,

Thanks for creating a post. Do you mind elaborating how these may be irrelevant as changes? 

Regards,
Subject7 Team

0
Comment actions Permalink
Avatar
Zach Schwantes

I believe these are irrelevant changes because most of the time when a user is wanting to understand last update date, they are thinking 'scripts changes', not just 'on the surface changes'. Surface changes are what I would consider things such as modifying names, change locked/unlocked state, change of owners, etc. These are attributes that do not affect the core script or the way testing is conducted.

0
Comment actions Permalink
Avatar
Rex Feizi

Hi Zach,

Thank you for sharing your observation. You raise an important point about the relevance of the last update date. However, for many projects, particularly in government and fintech industries with strict compliance requirements, tracking even seemingly minor changes is crucial.

For customers in these sectors, it’s essential to know exactly what has happened to any record, whether it’s a core script modification or a "surface change" like a name update or a state change (e.g., locked/unlocked). These details contribute to accountability and transparency.

We are actively enhancing our logging capabilities to ensure comprehensive tracking and are incorporating this level of detail into the UI to meet these compliance needs.

Thank you again for bringing this up.  Your input is always appreciated.

1
Comment actions Permalink
Avatar
Zach Schwantes

Hi Rex, 

This is great news! I have brought this up in a variety of posts, but it was mainly focused on the core point you mentioned which is logged capabilities to ensure comprehensive tracking has enough details for the end user. The issue I have with these dates is they mean nothing since we don't truly know what that date is referring to UNLESS we were the use to make this change. If a script let's say breaks, and I look at the last update date it may not be clear what changes. Does that mean the script was modified? Was the name changed? Was the script moved into a new folder? As of today we have no idea what this date truly means.

0
Comment actions Permalink

Please sign in to leave a comment.