Consistency in the UI (Created by/on, Modified by/on)

By the way, this post was prompted by a discussion I had with @alizee  this morning, she found in her SFDC connector new jobs that she ​​thought for a bit that were created by someone in her team without following proper governance… But I found the same “new” jobs on my end (not sure when they appeared, I can’t remember seeing them the last time I was in the Jobs screen checking up something) so we assumed they were jobs added by “System Administrator”. 

These gut checks and mini heart attacks could be avoided 😅

I would also like to add: there should be consistent display of execution statuses. In Connectors, we don’t see that a job is in progress. We can only see Success or Failure or Aborted, but it doesn’t show that a job is running (unless you go to activities from which you can’t abort anyway).

It should.

Adding other places I can think of:
Survey: 
(No created By/On, Modified by, and the “Modified on” co-exists with the “Responded Date” under “Date”)

Data Designer:
(Modified by/on are called Last Modified By and Last Modified Date respectively)

💯x💯

Adding another place:
In Data Management, after selecting an object, all four fields are missing: Created by, Created On, Modified by, Modified On 
 

+1 yes please! This is so important for us admins to help keep track of changes and when things were last updated in Gainsight.

Cross-posting a related idea: 
 

On a related note, having Created On would be a FANTASTIC aid while we start converting our programs, rules, templates, etc. to the new Horizon experience.

Having to use folders is awkward, and the “Model Name” field isn’t future-proof.

Labels (as long as they’re editable after publishing) would be helpful, but not what we’re looking for here.

This one sent us for a loop yesterday:
 

We were locked out of Gainsight for several hours, and the root cause was an unintended change by a user in the SAML configuration in Community, which impacted all the other platforms. Having "modified on/at" details for such changes would have saved us (and Support) significant time, resources, and headaches.

I still stand by what I said two years ago when I submitted the idea: “Besides consistency, it would go a long way in helping to troubleshoot changes. To be clear, in no way does this solve the need to have proper audit capabilities within GS, but it’s a starting point”
Please make this happen