victorwu

4 ms·

1.
by victorwu 8y ago
Thanks for the idea! We have the idea logged here: https://gitlab.com/gitlab-org/gitlab-ee/issues/1734 . Feel free to add comments there. Thanks!
2.
by victorwu 8y ago
Sean already did a great job responding to each point here. Just want to add one more quick one. We are working on key-value labels right now, and we think it will solve many of the problems of custom fields. Feel free to take a look and ad
3.
by victorwu 8y ago
--- As a user, I want to be notified by todos that only have any pending actions on them --- Can you explain further what you mean by "pending actions on them"? We are working to simplify and streamline our notifications and todos
4.
by victorwu 8y ago
I’m not aware that we intentionally changed anything with the line wraps. But if you go to User Settings > Preferences, you can select between Fixed vs Fluid layout width. Do you recall making any changes here recently? Here’s an issue w
5.
by victorwu 8y ago
If you have the Gold Plan (for a group) on GitLab.com, you will be able to use the Epics feature for that group. See [1]. If you have any other plan (including Free), you should not see that field (or at most you should see a dismissable up
6.
by victorwu 8y ago
In GitLab Starter, we have the export issues to CSV functionality, which includes two time tracking fields: time estimate and time spent. Is this the kind of reporting functionality you are looking for? https://docs.gitlab.com&#x
7.
by victorwu 8y ago
hitekker: See my edited comment above. We do not ship untested code. But any problems that users do find we definitely want them captured as soon as possible so that we can triage and fix.
8.
by victorwu 8y ago
Yep, GitLab releases on the 22nd of everyone month. Here’s a list of releases. https://about.gitlab.com/releases/
9.
by victorwu 8y ago
If you could log a bug here with any details that would be great! https://gitlab.com/gitlab-org/gitlab-ce Thanks! Edit: I wanted to clarify that if you’ve observed any undesirable behavior, we welcome you to log it and
10.
by victorwu 8y ago
Is there any particular time tracking feature you are interested in?
11.
by victorwu 8y ago
In addition to [0], to version-track issue/mr descriptions that was already referenced earlier (within an epic), we also have [1] open, to do the same for comments. Please feel free to comment more there! [0] https://gitlab.
12.
by victorwu 8y ago
We are continuing to improve our issue tracking / project management at different tiers. You can take a look at these epics and issues to see much of the work that we have already planned. Most of these issues are in Core or Starter:
13.
by victorwu 8y ago
Thank you for the explanation. I've created an issue. Feel free to continue the discussion there. https://gitlab.com/gitlab-org/gitlab-ce/issues/44553
14.
by victorwu 8y ago
Product manager at GitLab here. We welcome contributions! See https://about.gitlab.com/contributing/ and https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBU...
15.
by victorwu 8y ago
Here's an example of a blame on a previous commit of a file. https://gitlab.com/gitlab-org/gitlab-ce/blame/57ce7c655cc58e... Did you have some particular feature request beyond this view?
16.
by victorwu 8y ago
These are exactly the type of features we are focused on this year. Commenting on a block of code: https://gitlab.com/gitlab-org/gitlab-ce/issues/4143 Making a review session: https://gitlab.com&#x
17.
by victorwu 9y ago
Thanks for the feedback. Our goal of 10.0 was to release a version of group boards that serves the needs of large organizations. So we built the feature with multiple group boards in mind. We are considering bringing a version of group boar
18.
by victorwu 9y ago
Thank you for the feedback. As of GitLab 9.4, you are able to use both JIRA integration together with native GitLab issues. If JIRA integration is configured inside your GitLab project, the issues menu item in the navigation still goes to n
19.
by victorwu 9y ago
Inline editing is important design direction we are heading toward. The benefit is that you don't have to reload the entire page. And of course you can do single tasks, like updating labels / milestones / titles / descri
20.
by victorwu 9y ago
In particular, we've introduced a number of real-time features for issues in the past few releases. We are working to bring these to merge requests soon to get consistency. https://gitlab.com/gitlab-org/gitlab-ce&#
21.
by victorwu 9y ago
Thank you for the feedback. We're tracking how we can improve this functionality in this issue. Our design team is working hard on the merge request (the widget and the entire page) in general, and we are aiming to improve this part as
22.
by victorwu 9y ago
Thanks for the feedback regarding editing merge requests. In this release, we brought inline editing to issues. (So you don't have to do a full page load, like you mentioned.) So we will definitely bring this concept to merge requests
23.
by victorwu 9y ago
Thanks for the feedback. Indeed we recognize the inconsistencies in the UI from search to other areas. Rather than overhaul entire GitLab with each new improvement, we typically apply the change to one area first, and incrementally bring it
24.
by victorwu 9y ago
Thank you for the feedback regarding commenting on merge requests. The diff view is indeed very important for collaboration. In the upcoming 9.2 release (slated for May 22nd), we are adding the ability to comment on older versions of the co
25.
by victorwu 9y ago
You are referring to this one right? https://gitlab.com/gitlab-org/gitlab-ee/issues/1906 . Yes, it is currently marked as an EE feature. And Sid linked to the dependent issues feature below. Both of these feat
26.
by victorwu 9y ago
Thanks. Feel free to add feedback to the ongoing discussion here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29835 .
27.
by victorwu 9y ago
We also have a new research panel, which includes usability texting. Anyone is welcome to join to provide further feedback, which will significantly impact our product development. https://about.gitlab.com/researchpanel&#x2F
28.
by victorwu 9y ago
Thanks for the feedback! In this iteration, we think recovering more space helps users focus on content, and allows them to see more content at once. Definitely we recognize the tradeoff of additional clicks and discoverability as a result.
29.
by victorwu 9y ago
Thank you for the feedback. The sidebar is indeed oft-discussed. And we don't claim we have all the right answers. We work hard every iteration to make the best decision, ship updates, and get feedback. This is the issue where we discu
30.
by victorwu 9y ago
We originally built GitLab with that use case of a single repo in mind. Create a GitLab project, and you have a single repository for code. We know this is an important use case for many teams, because of it's straightforward, simple s

More ›