BUG: teams and users tables missing updated_at triggers

[g-k-s-03]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Problem

In main, only the tickets table has an updated_at trigger.
The teams and users tables are missing it, causing inconsistent
timestamp tracking across the database.

Current Behavior

• tickets → has updated_at trigger ✓
• teams → missing updated_at trigger ✗
• users → missing updated_at trigger ✗

Expected Behavior

All three tables should automatically update the updated_at
column whenever a row is modified.

Fix

Add update_updated_at_column() trigger to both
teams and users tables.

Impact

Low — not breaking anything but causes inconsistent
timestamp data across tables.

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

[g-k-s-03]

@jddeep , @SharkyBytes, Hi, I am already working on this locally as part of a
larger database improvement. Will raise a PR soon.

Please assign this issue to me.

[dhruvi-16-me]

Hello @g-k-s-03 If you don't mind, can I work on this issue? I think I also encountered this issue a few days earlier.

[g-k-s-03]

@dhruvi-16-me, as I am working on another issue, you can work on this.

[dhruvi-16-me]

@g-k-s-03 Thanks