Make the design management LFS placeholder dismissible
Problem to solve
As a user who doesn't want to enable LFS, I want to dismiss the design management text so I can reduce the visual clutter in issues.
Currently the the page shows a persistent info about LFS;
We want it to become a dismissible alert as mentioned in the attached design of this issue.
Proposal
Make the LFS placeholder message dismissible. Use the recommended Pajamas component (banner). Once dismissed, don't show it again for that user, even on new issues.
Designs
- Show closed items
Relates to
- #230286Backlog
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Matthew Nearents added Category:Design Management devopscreate typefeature workflowdesign + 1 deleted label
added Category:Design Management devopscreate typefeature workflowdesign + 1 deleted label
- Author Contributor
fyi @cdybenko
Edited by Matthew Nearents Collapse replies - Contributor
Awesome, thanks!
- Matthew Nearents added 1 design
added 1 design
- Matthew Nearents mentioned in design management/design #230538 (closed)[LFS_minimal_4.png]
mentioned in design management/design #230538 (closed)[LFS_minimal_4.png]
- Christen Dybenko changed milestone to %Backlog
changed milestone to %Backlog
- Christen Dybenko added to epic &3964
added to epic &3964
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
I would like to support this idea. Upon upgrading our Omnibus install, the result was immediate confusion on the part of all parties involved. Enabling this for older Gitlab installations takes time and effort that isn't clear (Git LFS, rake tasks, etc) to the end user. Turning off the banner will provide administrators with much needed breathing room.
2- Matthew Nearents mentioned in issue #229537 (closed)
mentioned in issue #229537 (closed)
- Matthew Nearents marked this issue as related to #230599 (closed)
marked this issue as related to #230599 (closed)
- Matthew Nearents removed the relation with #230599 (closed)
removed the relation with #230599 (closed)
- Matthew Nearents started a discussion on LFS_minimal_4.png
started a discussion on LFS_minimal_4.png
- Matthew Nearents assigned to @mnearents
assigned to @mnearents
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
- 🤖 GitLab Bot 🤖 added sectiondev label
added sectiondev label
- Matthew Nearents added 1 design
added 1 design
- Christen Dybenko started a discussion on lfs_alert.png
started a discussion on lfs_alert.png
- Matthew Nearents started a discussion on lfs_alert.png
started a discussion on lfs_alert.png
- Matthew Nearents removed 1 design
removed 1 design
- Matthew Nearents updated 1 design
updated 1 design
Collapse replies - Developer
I’m not seeing anything either. @mnearents is anything needed here from @vicbell?
- Author Contributor
@vicbell @jeldergl there's an archived design in Version 2 (dropdown above) that uses the Pajamas Banner. If we wanted to go that route, versus a basic alert, it would need an illustration. We decided to move forward with the alert to keep moving, but we could update to a banner later if we thought it would be better.
- Developer
Ah, yeah we don’t include illustrations in alerts so I would still to the current path. Thanks for filling us in!
- Author Contributor
@jeldergl @vicbell in Version 2 of the designs there is a Banner element with an illustration placeholder.
Edited by Matthew Nearents - Author Contributor
@cdybenko I think this can move to planning breakdown
- Matthew Nearents unassigned @mnearents
unassigned @mnearents
- Matthew Nearents removed workflowdesign label
removed workflowdesign label
- Matthew Nearents added workflowplanning breakdown label
added workflowplanning breakdown label
- Contributor
Collapse replies - Contributor
@cdybenko Would that be dismissable with local storage save so it's not showing up on the same machein again?
- Developer
- Contributor
@mvanremmerden, @mikelong, this issue was with groupknowledge but now I'd need to prioritize it within Plan.
I'm adding Next Up for prioritized design issues coming from groupknowledge
- Developer
- Contributor
@donaldcook I'm using that label to signify anything from Design Management or of interest to be weighted next.
- Christen Dybenko changed milestone to %13.6
changed milestone to %13.6
- Christen Dybenko added frontend label
added frontend label
- Matt Nohr added Backlog RefinementKnowledge label
added Backlog RefinementKnowledge label
- 🤖 GitLab Bot 🤖 mentioned in issue #273525 (closed)
mentioned in issue #273525 (closed)
- Matt Nohr removed Backlog RefinementKnowledge label
removed Backlog RefinementKnowledge label
- Takuya Noguchi marked this issue as related to #230286
marked this issue as related to #230286
- Marcel van Remmerden mentioned in issue create-stage#12768 (closed)
mentioned in issue create-stage#12768 (closed)
- Marcel van Remmerden added UX FY21-Q4 featureenhancement labels
added UX FY21-Q4 featureenhancement labels
- 🤖 GitLab Bot 🤖 changed milestone to %13.7
changed milestone to %13.7
- 🤖 GitLab Bot 🤖 added missed:13.6 label
added missed:13.6 label
- Christen Dybenko removed milestone %13.7
removed milestone %13.7
- Christen Dybenko added Next Up label
added Next Up label
- Matt Nohr added groupproduct planning label and removed 1 deleted label
added groupproduct planning label and removed 1 deleted label
- Matt Nohr added devopsplan label and removed devopscreate label
added devopsplan label and removed devopscreate label
- Alexis Ginsberg mentioned in issue gitlab-com/Product#1761 (closed)
mentioned in issue gitlab-com/Product#1761 (closed)
- Donald Cook set weight to 2
set weight to 2
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1244 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1244 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1330 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1330 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1414 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1414 (closed)
- Christen Dybenko changed milestone to %Backlog
changed milestone to %Backlog
- Christen Dybenko removed Next Up label
removed Next Up label
- Kushal Pandya changed the description
Compare with previous version changed the description
- Maintainer
@amandarueda This may be another good onboarding candidate, wdyt?
1 - Amanda Rueda added onboarding label
added onboarding label