Project

General

Profile

Actions

Feature #94459

closed

be_user admin as Timestamp

Added by Tomas Norre Mikkelsen over 3 years ago. Updated 5 months ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2021-07-01
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Needs Decision

Description

Hi,

I listened to a Laravel Podcast recently, and they suggested using booleans like isAdmin with timestamps instead of only 0 or 1.

The idea behind this is, that we have additional data like: isAdminSince, as the timestamp of the time when the user received the admin status is stored instead of just 1. When removing the privilege again, this is set to 0.

This will in my opinion also help to locate issues internally if someone gains/gets admin access, as we would be able to see since when they had this access.

I would be happy to do the implementation, if someone votes for this feature.

Actions #1

Updated by Georg Ringer 5 months ago

  • Sprint Focus set to Needs Decision
Actions #2

Updated by Georg Ringer 5 months ago

  • Status changed from New to Rejected

Hey,

I discussed this with Christian Kuhn and we came to the conclusion that we don't want to go this way because of:

- all queries would need to be changed and also user are trained differently
- we got the history for that

if you don't agree, feel free to contact me via slack!

Actions

Also available in: Atom PDF