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
Expand Organization Dashboard #2355
Comments
/cc @getsentry/team |
👍 What's the incentive for doing this organization-wide vs project-wide? Would it be potentially too much for a whole org? Will any of this be personalized for an individual? Like, "issues assigned to me" vs "issues assigned to others". I'm thinking of the Phabricator dashboard here. |
@mattrobenolt this would be our version of the Phabricator dash. Organization dash makes a lot more sense as if you work on multiple projects its a mess to dig through things. |
I sketched an initial stab at this: There's quite a lot going on, but I think I prefer that to the snoozefest that exists currently. My biggest concerns are:
Curious to hear everyone's feedback. |
Various thoughts/feedback:
|
👍 |
More notes:
|
Thinking about this, i wonder if we could put assign to under the selector as well? I still wanna have the barchart there, so if we hid all CTAs under the same action bar it'd make it much easier to fit the chart in there. |
I've got Assigned, Bookmarked, and History (Viewed) done in the branch. We need visuals for the |
Some initial bits, which power "My Issues" (we could rename this to Issues) are merged behind a feature switch. Any getsentry.com users can reach out to us if they want to opt-in. |
/cc @ckj |
hid assignee selector, implemented the other actions, just needs visuals now (i think) |
Some basic work is available in /cc @ckj |
@ckj did the organization-wide dashboard at #2355 (comment) ever became available ? |
Some things we could show that are useful:
Some things will be more complicated to do organization-wide so we should tread carefully. Its also likely a lot of these could make their way into the project dashboard.
We should focus this on workflow features less so than data dumps.
The text was updated successfully, but these errors were encountered: