21–30 of 128 posts
We're super proud of this release. As always, we're here for any questions or comments.
I have yet to understand where this kanban board stuff makes sense. Apparently, the Agile philosophy [0] introduced this to the software development world. Most implementations (Gitlab, Wekan) seem to miss central features (limits, cycle time stats). I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? R…
I have yet to understand where this kanban board stuff makes sense. Apparently, the Agile philosophy [0] introduced this to the software development world. Most implementations (Gitlab, Wekan) seem to miss central features (limits, cycle time stats). I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? R…
I'm not sure we want to have the software enforce limits, but I do agree that you don't want any list/column to become too long.
Cycle time analytics are planned in https://gitlab.com/gitlab-org/gitlab-ce/issues/20975
We're super proud of this release. As always, we're here for any questions or comments.
Since using Asana, one feature I want in every project management / issue management tool is the @mention [0]. Asana's @mention allows you to link other tasks or issues very conveniently. Just like HipChat's commands feature mentioned in your release notes, Asana's @mention feature is extremely convenient. [0]: https://asana.com/guide/help/fundamentals/text
I have yet to understand where this kanban board stuff makes sense. Apparently, the Agile philosophy [0] introduced this to the software development world. Most implementations (Gitlab, Wekan) seem to miss central features (limits, cycle time stats). I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? R…
Each week we meet with project owners (somebody at the client company). They give us a list of tasks they want completed this week and we go over tasks we finished last week.
After the project is done, we move to only working on one-off issues they send. Usually bugs or small new feature requests. A simple issue tracker would work fine here, but we still have weekly meeting with our boss to show that we actually did work last week.
We already use self-hosted GitLab for our code, so I want to try out this new board feature to see if it meets our needs.
We're super proud of this release. As always, we're here for any questions or comments.
New features look awesome. Any idea of when we'll get global search? For a long time I've been wanting to search for a particular code snippet or file name across all projects.
I just migrated our companies repos away from Bitbucket to GitLab. The whole process was super-easy. Really happy so far!
Is it a matter of taste or Github's UI indeed looks more professional than Gitlab's one? I've tried to switch from GH to GL hosted for my personal projects multiple times and no luck. I like the fact that Gitlab is open-source and it has a lot of features but I still don't feel comfortable using it. Any opinions and preferences on GH's UI vs. GL's UI?
GitHub has a better container in their CSS. GitLab defaults to letting text lines be overly long and this just makes the whole thing feel uncomfortable even if you think you don't mind it. Otherwise, I think GitLab is largely alright UI.