On Mon, May 29, 2023 at 1:29 AM Johannes Zarl-Zierl
wrote:
> Am Samstag, 27. Mai 2023, 23:13:08 CEST schrieb Ben Cooksley:
> > On Sun, May 28, 2023 at 8:24 AM Johannes Zarl-Zierl <
> johan...@zarl-zierl.at>
> > wrote:
> > > I'm fine with having columns be mapped as labels.
> > > However, if it is
Am Samstag, 27. Mai 2023, 23:13:08 CEST schrieb Ben Cooksley:
> On Sun, May 28, 2023 at 8:24 AM Johannes Zarl-Zierl
> wrote:
> > I'm fine with having columns be mapped as labels.
> > However, if it is easy to implement, having some columns be converted to
> > milestones would be quite nice, since
On Sun, May 28, 2023 at 8:24 AM Johannes Zarl-Zierl
wrote:
> That's great news!
>
> Am Montag, 22. Mai 2023, 17:17:50 CEST schrieb Wolthera:
> > Overall, I've noticed that milestones are best for collecting tasks
> > related to a release or a defined project (Say, a new tool, importer
> > or work
That's great news!
Am Montag, 22. Mai 2023, 17:17:50 CEST schrieb Wolthera:
> Overall, I've noticed that milestones are best for collecting tasks
> related to a release or a defined project (Say, a new tool, importer
> or workflow), while the boards are better for if you need to track the
> state
What's the plan for sys admin tickets currently needed to publish releases?
May 26, 2023 5:10:43 PM Ben Cooksley :
> On Fri, May 26, 2023 at 9:31 AM Nate Graham wrote:
>> On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks
>> have no real "home"; they just have project
>>>
On Fri, May 26, 2023 at 9:31 AM Nate Graham wrote:
> On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks
> have no real "home"; they just have project
> > tags, and they can have multiple such tags to be able to belong to
> > multiple projects. For example "VDG" and als
Having used it for some years at Boeing, I find that gitlab has a competent
task management capability in the form of Issues. While at Boeing, and
apparently at JP Morgan Chase, there was also an alternative (WIP
Work-In-Progress tool in Boeing-speak) in the form of Jira (integrated with
gitlab),
On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks
have no real "home"; they just have project
tags, and they can have multiple such tags to be able to belong to
multiple projects. For example "VDG" and also "Plasma". Such a Task
shows up in both projects' workboar
> > Also, in Phabricator, Tasks have no real "home"; they just have project
> > tags, and they can have multiple such tags to be able to belong to
> > multiple projects. For example "VDG" and also "Plasma". Such a Task
> > shows up in both projects' workboards. But in GitLab, Issues need to
> > liv
On Tue, May 23, 2023 at 11:39 AM Nate Graham wrote:
> Great, this will be a good thing to have behind us.
>
You can say that again.
Phabricator is a bit of a nightmare to host - in large part because the
entire content of our Subversion repository is indexed in it's database,
which has resulted
Great, this will be a good thing to have behind us.
Because workboards in GitLab are Label-driven via automation, I think we
would have to make each workboard column in Phabricator transform into a
custom label in GitLab so that Tasks' positions in workboards can be
preserved when they move to
Great, pretty excited for the tasks to move to issues :)
On Sun, May 21, 2023 at 9:01 PM Ben Cooksley wrote:
>
> On Sun, May 21, 2023 at 10:10 PM Johnny Jazeix wrote:
>>
>>
>> Also, some phabricator tasks have hierarchy, is there an equivalent in
>> gitlab? There are tasks in gitlab too but I'm
On Sun, May 21, 2023 at 10:10 PM Johnny Jazeix wrote:
> Hi,
> Le dim. 21 mai 2023 à 11:15, Ben Cooksley a écrit :
>
>> Hi all,
>>
>> As many of you will undoubtedly be aware, we currently have a bit of a
>> hybrid approach with our use of GitLab, with some projects/areas still
>> making use of P
Hi,
Le dim. 21 mai 2023 à 11:15, Ben Cooksley a écrit :
> Hi all,
>
> As many of you will undoubtedly be aware, we currently have a bit of a
> hybrid approach with our use of GitLab, with some projects/areas still
> making use of Phabricator as they await the final import of these tasks
> across
Hi all,
As many of you will undoubtedly be aware, we currently have a bit of a
hybrid approach with our use of GitLab, with some projects/areas still
making use of Phabricator as they await the final import of these tasks
across to GitLab.
That time has now arrived, as Phabricator is long since u
15 matches
Mail list logo
