On 5/18/20 11:05 PM, Bhushan Shah wrote:
For Gitlab best way to filter/track anything is labels and existing
states like, open/closed
So one way to for instance list all VDG issues and merge requests would
be,
If we use Issues in each individual project for tasks, wouldn't this
complicate eventually migrating from Bugzilla to GitLab issues, since it
would intermingle the user bug reporting function with developer task
tracking and communication?
Nate
On 5/18/20 10:59 PM, Bhushan Shah wrote:
On
On Mon, May 18, 2020 at 08:29:42PM -0600, Nate Graham wrote:
> In Phab, a task can exist in multiple projects' workboards, which is useful
> for tracking VDG-related work across multiple projects. This is something I
> wouldn't want to lose, but maybe we can approximate it somehow in GitLab?
For
On Tue, May 19, 2020 at 07:08:59AM +0530, Bhushan Shah wrote:
> > - Do we want to keep issues enabled and use them for "tasks"?
> > - Do we want to have separate "tasks" boards under invent.kde.org/teams ?
> > Nico: vote for 2
> > Marco: vote for 2
I am in highly favor of the option 1, for
In Phab, a task can exist in multiple projects' workboards, which is
useful for tracking VDG-related work across multiple projects. This is
something I wouldn't want to lose, but maybe we can approximate it
somehow in GitLab?
Nate
On 5/18/20 7:38 PM, Bhushan Shah wrote:
Hello!
On Mon, May
Hello!
On Mon, May 18, 2020 at 01:20:07PM +0200, Marco Martin wrote:
> Bhushan: We have few questions at this point
> - Do we want to keep issues enabled and use them for "tasks"?
> - Do we want to have separate "tasks" boards under invent.kde.org/teams ?
> Nico: vote for 2
> Marco: vote for
