-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardize the column names on Events tabs #3376
Standardize the column names on Events tabs #3376
Comments
@LappleApple , Do we need to Standardize events as well in OSS as it's already the same in Application & Image Automation . |
@TheGostKasper Yes please (on standardizing in OSS) :) |
@TheGostKasper When you say "that will affect the EE after using that EventTable where it's not used in EE," could you elaborate on "affect"--what will be the effect(s)? Thanks much |
What will happen actually is that i'll use
|
Got it, thanks much for the info. cc'ing @jpellizzari for awareness about the underneath-the-hood aspects |
redirect3-2023-10-02_13.45.47.mp4@LappleApple @mmoulian , Do we need any changes to the Reason + icon ? |
Hi @TheGostKasper: I'd revise the tooltip text slightly to say: "This refers to what triggered the event, and can vary by component." |
Currently some of our Events tabs use wording that is different from other Events tabs. But there's just one schema for Event objects. To prevent user confusion, let's standardize so that every Events tab includes these four column names:
This involves the views:
Acceptance Criteria:
Location of the requested change
Correct names:
Incorrect names:
The text was updated successfully, but these errors were encountered: