Designs currently exist in a separate tab inside of an issue making discoverability of the designs challenging. Users are only provided a number indication that designs exist which limits the visual queue of an area intended for visual items.
Intended users
Users who interact and provide feedback on designs. As well as those users looking to gain information on an issue and all of the components that may be involved.
Further details
Feature discovery of Design Management is challenging as the designs are hidden in a tab that may not make it clear to users that designs are present on the issue.
Proposal
At the bottom of the issue a section similar to Related issues should be added that shows the available design thumbnails of an issue. This provides easier access to the designs and more important information to the users looking at issues.
Empty State
Permissions and Security
The box should only be available on issues for users that have the appropriate license to utilize Design Management.
What does success look like, and how can we measure that?
Increased visibility of the designs feature will help to increase adoption across organization. By adding this extra visibility here we should see more discussions happening on Designs.
Not to derail here--just another thought, Jira provides a similar feature that's kept more broadly to attachments in general. Since designs are typically served as attachments, maybe it's best to be more broad here?
I could see this benefitting devs that are sharing screenshots, JSON files, architectural API diagrams, etc. related to an issue. But then it becomes less about "design" management and more just "knowledge" management.
Not to derail here--just another thought, Jira provides a similar feature that's kept more broadly to attachments in general. Since designs are typically served as attachments, maybe it's best to be more broad here?
That's a very interesting idea, I like it! It goes back to "Everybody is a designer", and that means artifacts from other professions could be treated exactly the same as e.g. wireframes.
I mocked up a quick and dirty concept here in Figma.
I'm not entirely happy with the segmented controls within a dropdown, so perhaps two buttons is a better route (probably more accessible too), but it's hopefully enough to convey the thought. This way, everyone could have structured discussions around pinned files. I'm not sure how/if comments would extend to embedded links since they take you out of the GitLab context.
I mocked up a quick and dirty concept here in Figma.
Great job, I like it, thanks a lot! :)
I'm not sure how/if comments would extend to embedded links since they take you out of the GitLab context.
That's a great question, and I'm not sure we have the answer to that already. I think this is something we will have to have some more strategic discussions and research around. Our focus is to make GitLab the single source of truth. However, as the Product Designer persona is new for us, we need to understand how much this approach impacts their workflow and how we can manage that.
For example, as a Designer, I will often have to act on the comments of the designs that I uploaded and change certain aspects. When I use e.g. Sketch Cloud to share and upload my designs, I directly have these comments within the Sketch environment. This means I have all information right at the place where I have to act on it, making this process super smooth and fast. When that discussion around the designs is happening inside of GitLab, I suddenly have to have two systems open to read on the comments and change the designs, which is disrupting my workflow. We still have to understand better how that workflow can be simplified and improved with GitLab.
Christen Dybenkochanged title from Design widget should provide thumbnails in Issue Descriptions to The design tab should be more visible in the Issue UI so design thumbnails are easily seen
changed title from Design widget should provide thumbnails in Issue Descriptions to The design tab should be more visible in the Issue UI so design thumbnails are easily seen
Christen Dybenkochanged title from The design tab should be more visible in the Issue UI so design thumbnails are easily seen to The design tab should be more visible in the Issue UI
changed title from The design tab should be more visible in the Issue UI so design thumbnails are easily seen to The design tab should be more visible in the Issue UI
Christen Dybenkochanged title from The design tab should be more visible in the Issue UI to Make the Design Collection should be more visible in the Issue UI
changed title from The design tab should be more visible in the Issue UI to Make the Design Collection should be more visible in the Issue UI
Darva Satcherchanged title from Make the Design Collection should be more visible in the Issue UI to Make the Design Collection more visible in the Issue UI
changed title from Make the Design Collection should be more visible in the Issue UI to Make the Design Collection more visible in the Issue UI
@cdybenko Are you referring to the Sticky Issue Title issue we're working on? If so, we've discussed a follow-on issue to make the navigation tabs sticky on issues, like they are on MRs, which could improve the visibility of the Designs tab.
@cdybenko yea let's discuss. The core problem we are starting to experience with issues is that we are accruing "clutter" in the main content area with a steadily growing list of things that may or may not be used by various teams/users. This is only going to become more apparent and bothersome once we add tasks, surface requirements in issues, better link incidents and/or vulnerabilities, etc. I think we need to step back and rethink the interaction model on issues as a whole. Would love to bounce some ideas around with groupknowledge and groupproject management
@mikelong@gweaver@mnearents I'm on board for teaming up on this, whether it is a sticky tab or a complication for a grid of thumbnails that sits nicely under the description.