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 add some comments. Thanks!
---
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 in GitLab. In particular, the current thinking is that they are very similar. A "notification" is an email, and a "todo" is a something that GitLab calls your attention to in the Web UI to take action on. So mechanically, they are very similar and we would like to harmonize them.
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 upgrade UI). That doesn’t seem to be case currently. I’ve logged an issue to correct this. [2]
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?
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.
Edit: I wanted to clarify that if you’ve observed any undesirable behavior, we welcome you to log it and we will address it as soon as we can. I see how my original comment made it seem like we ship untested code. That’s not the case as Sid mentioned below. That being said, there might be specific edge cases or scenarios we have not captured in our tests. So problems do appear from time to time. So I wanted to invite anybody to log any problem so that we can reproduce it as soon as we can and get it fixed.
Also as Sid mentioned, this feature was recently brought to Core so that more users now have access to it.
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!
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:
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 boards to CE as many of our users are telling us it makes sense for smaller organizations as well.
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 native GitLab issues, and you can use GitLab issues as usual.
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 / descriptions all independently and separately, providing a more web-app-like experience, instead of a website experience. Ultimately, it's more usable and efficient.
In particular for the issue / merge request description areas, we want to get to a more collaborative design in the future when you can see other users making changes in super near-real-time, almost like Google docs. Currently, our issue descriptions already are updated in real-time, but it takes a few seconds for you to see updates. So we are working hard in this direction and we appreciate the validation that inline editing makes sense.
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.