Foreman core and smart-proxy projects both have a policy of having a
Redmine ticket for each PR (new projects are likely to adopt the same
policy). As we are using Trello for planning and keeping track of
progress during sprints, at least some of this information needs to be
present there as well.
In an attempt to reduce duplication and the number of places where
information is located, I propose to phase out Trello and switch to
Redmine exclusively for all bug- and story-tracking needs.
Thoughts?
-d
There's a "Backlog" custom field that's enabled on a few projects for
this purpose.
I don't think the two are equivalent though. For instance, I wouldn't
want to see a design task added in Redmine. I think stories often break
down into more tasks and individual tickets, so represent a higher level
description or goal.
My (slight) preference is to see both get used, but to keep Trello clear
of implementation details and leave that to Redmine or PRs.
···
On 13/08/13 13:25, Dmitri Dolguikh wrote:
> Foreman core and smart-proxy projects both have a policy of having a
> Redmine ticket for each PR (new projects are likely to adopt the same
> policy). As we are using Trello for planning and keeping track of
> progress during sprints, at least some of this information needs to be
> present there as well.
>
> In an attempt to reduce duplication and the number of places where
> information is located, I propose to phase out Trello and switch to
> Redmine exclusively for all bug- and story-tracking needs.
>
> Thoughts?
–
Dominic Cleal
Red Hat Engineering
I aggree. Compared to Trello our Redmine as it is now misses some notion
of what is planned for current sprint. I think this can be fixed by
adding a custom field. Then we have a tool with equivalent power.
+1 for moving to Redmine
T.
···
On 08/13/2013 02:25 PM, Dmitri Dolguikh wrote:
> Foreman core and smart-proxy projects both have a policy of having a
> Redmine ticket for each PR (new projects are likely to adopt the same
> policy). As we are using Trello for planning and keeping track of
> progress during sprints, at least some of this information needs to be
> present there as well.
>
> In an attempt to reduce duplication and the number of places where
> information is located, I propose to phase out Trello and switch to
> Redmine exclusively for all bug- and story-tracking needs.
>
> Thoughts?
> -d
What Dominic said, with the extra point that we have invested some time in
the Trello / Github PR integration, and I don't want to lose that - the
ability to track the state of PRs at a glance is very useful. There are
alternative's of course, but given it already works…
>> Foreman core and smart-proxy projects both have a policy of having a
>> Redmine ticket for each PR (new projects are likely to adopt the same
>> policy). As we are using Trello for planning and keeping track of
>> progress during sprints, at least some of this information needs to be
>> present there as well.
>>
>> In an attempt to reduce duplication and the number of places where
>> information is located, I propose to phase out Trello and switch to
>> Redmine exclusively for all bug- and story-tracking needs.
>>
>> Thoughts?
>
> There's a "Backlog" custom field that's enabled on a few projects for
> this purpose.
>
> I don't think the two are equivalent though. For instance, I wouldn't
> want to see a design task added in Redmine. I think stories often break
> down into more tasks and individual tickets, so represent a higher level
> description or goal.
Can we modify values of the field Tracker? Current values are "Bug,
Feature, Support, Refactor".I can see adding "Design" there as a way to go.
···
On 08/13/2013 02:36 PM, Dominic Cleal wrote:
> On 13/08/13 13:25, Dmitri Dolguikh wrote:
My (slight) preference is to see both get used, but to keep Trello clear
of implementation details and leave that to Redmine or PRs.
One way could be adding a specific tracker for this. Second option is to use
subtasks, so the implementation tasks will be children of design task. This
way you'll see the progress and all information on one place.
For myself I'd like to see everything in redmine. I think having one tool is
always better. Just PR review board should stay as it is now. However at least
moving sprint work to redmine is a good step for me.
···
On Tuesday 13 of August 2013 13:36:22 Dominic Cleal wrote:
> On 13/08/13 13:25, Dmitri Dolguikh wrote:
> > Foreman core and smart-proxy projects both have a policy of having a
> > Redmine ticket for each PR (new projects are likely to adopt the same
> > policy). As we are using Trello for planning and keeping track of
> > progress during sprints, at least some of this information needs to be
> > present there as well.
> >
> > In an attempt to reduce duplication and the number of places where
> > information is located, I propose to phase out Trello and switch to
> > Redmine exclusively for all bug- and story-tracking needs.
> >
> > Thoughts?
>
> There's a "Backlog" custom field that's enabled on a few projects for
> this purpose.
>
> I don't think the two are equivalent though. For instance, I wouldn't
> want to see a design task added in Redmine. I think stories often break
> down into more tasks and individual tickets, so represent a higher level
> description or goal.
--
Marek
> From: "Dmitri Dolguikh" <witlessbird@gmail.com>
> To: foreman-dev@googlegroups.com
> Sent: Tuesday, August 13, 2013 9:47:29 AM
> Subject: Re: [foreman-dev] Trello and/or Redmine?
>
> I think it's possible to switch to Redmine exclusively; I think we wouldn't
> need to introduce additional/custom fields - what I currently see in
> Redmine should suffice. In some ways it would even be an improvement -
> searching/filtering in Redmine is significantly better compared to Trello,
> for example. Redmine lacks a clean way to create parent story - children
> tasks associations though, which may become a hassle very quickly.
>
> Dominic - we could use Trello for backlog and backlog grooming only, and
> switch to Redmine for any work being allocated for/performed during sprint:
> we'd move stories from Trello to Redmine during sprint planning. Is
> everybody ok with this approach?
Given the fact that neither tool seems to work well for us, why not consider something completely different? I don't want to start a total bikeshed here, but I think we should consider switching tools altogether instead of switching back and forth between Trello and Redmine constantly.
Jira has my vote (and is free for OSS projects), but I'm totally open to other solutions, too.
···
----- Original Message -----
-d
On Tue, Aug 13, 2013 at 2:08 PM, Dominic Cleal dcleal@redhat.com wrote:
On 13/08/13 13:54, Tomas Strachota wrote:
On 08/13/2013 02:36 PM, Dominic Cleal wrote:
On 13/08/13 13:25, Dmitri Dolguikh wrote:
Foreman core and smart-proxy projects both have a policy of having a
Redmine ticket for each PR (new projects are likely to adopt the same
policy). As we are using Trello for planning and keeping track of
progress during sprints, at least some of this information needs to be
present there as well.
In an attempt to reduce duplication and the number of places where
information is located, I propose to phase out Trello and switch to
Redmine exclusively for all bug- and story-tracking needs.
Thoughts?
There’s a “Backlog” custom field that’s enabled on a few projects for
this purpose.
I don’t think the two are equivalent though. For instance, I wouldn’t
want to see a design task added in Redmine. I think stories often break
down into more tasks and individual tickets, so represent a higher level
description or goal.
Can we modify values of the field Tracker? Current values are “Bug,
Feature, Support, Refactor”.I can see adding “Design” there as a way to
go.
Yes, we can add new tracker types. It’s possible to change which fields
are used on each type of tracker.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
We're talking about the backlog board, not PR tracking.
···
On 13/08/13 13:41, Greg Sutcliffe wrote:
> What Dominic said, with the extra point that we have invested some time
> in the Trello / Github PR integration, and I don't want to lose that -
> the ability to track the state of PRs at a glance is very useful. There
> are alternative's of course, but given it already works...
–
Dominic Cleal
Red Hat Engineering
Yes, we can add new tracker types. It's possible to change which fields
are used on each type of tracker.
···
On 13/08/13 13:54, Tomas Strachota wrote:
> On 08/13/2013 02:36 PM, Dominic Cleal wrote:
>> On 13/08/13 13:25, Dmitri Dolguikh wrote:
>>> Foreman core and smart-proxy projects both have a policy of having a
>>> Redmine ticket for each PR (new projects are likely to adopt the same
>>> policy). As we are using Trello for planning and keeping track of
>>> progress during sprints, at least some of this information needs to be
>>> present there as well.
>>>
>>> In an attempt to reduce duplication and the number of places where
>>> information is located, I propose to phase out Trello and switch to
>>> Redmine exclusively for all bug- and story-tracking needs.
>>>
>>> Thoughts?
>>
>> There's a "Backlog" custom field that's enabled on a few projects for
>> this purpose.
>>
>> I don't think the two are equivalent though. For instance, I wouldn't
>> want to see a design task added in Redmine. I think stories often break
>> down into more tasks and individual tickets, so represent a higher level
>> description or goal.
>
> Can we modify values of the field Tracker? Current values are "Bug,
> Feature, Support, Refactor".I can see adding "Design" there as a way to go.
–
Dominic Cleal
Red Hat Engineering
I think it's possible to switch to Redmine exclusively; I think we wouldn't
need to introduce additional/custom fields - what I currently see in
Redmine should suffice. In some ways it would even be an improvement -
searching/filtering in Redmine is significantly better compared to Trello,
for example. Redmine lacks a clean way to create parent story - children
tasks associations though, which may become a hassle very quickly.
Dominic - we could use Trello for backlog and backlog grooming only, and
switch to Redmine for any work being allocated for/performed during sprint:
we'd move stories from Trello to Redmine during sprint planning. Is
everybody ok with this approach?
-d
···
On Tue, Aug 13, 2013 at 2:08 PM, Dominic Cleal wrote:
On 13/08/13 13:54, Tomas Strachota wrote:
On 08/13/2013 02:36 PM, Dominic Cleal wrote:
On 13/08/13 13:25, Dmitri Dolguikh wrote:
Foreman core and smart-proxy projects both have a policy of having a
Redmine ticket for each PR (new projects are likely to adopt the same
policy). As we are using Trello for planning and keeping track of
progress during sprints, at least some of this information needs to be
present there as well.
In an attempt to reduce duplication and the number of places where
information is located, I propose to phase out Trello and switch to
Redmine exclusively for all bug- and story-tracking needs.
Thoughts?
There’s a “Backlog” custom field that’s enabled on a few projects for
this purpose.
I don’t think the two are equivalent though. For instance, I wouldn’t
want to see a design task added in Redmine. I think stories often break
down into more tasks and individual tickets, so represent a higher level
description or goal.
Can we modify values of the field Tracker? Current values are “Bug,
Feature, Support, Refactor”.I can see adding “Design” there as a way to
go.
Yes, we can add new tracker types. It’s possible to change which fields
are used on each type of tracker.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
>
> I think it's possible to switch to Redmine exclusively; I think we
wouldn't need to introduce additional/custom fields - what I currently see
in Redmine should suffice. In some ways it would even be an improvement -
searching/filtering in Redmine is significantly better compared to Trello,
for example. Redmine lacks a clean way to create parent story - children
tasks associations though, which may become a hassle very quickly.
>
> Dominic - we could use Trello for backlog and backlog grooming only, and
switch to Redmine for any work being allocated for/performed during sprint:
we'd move stories from Trello to Redmine during sprint planning. Is
everybody ok with this approach?
+1
>
> -d
>
>
>>
>> >>> Foreman core and smart-proxy projects both have a policy of having a
>> >>> Redmine ticket for each PR (new projects are likely to adopt the same
>> >>> policy). As we are using Trello for planning and keeping track of
>> >>> progress during sprints, at least some of this information needs to
be
>> >>> present there as well.
>> >>>
>> >>> In an attempt to reduce duplication and the number of places where
>> >>> information is located, I propose to phase out Trello and switch to
>> >>> Redmine exclusively for all bug- and story-tracking needs.
>> >>>
>> >>> Thoughts?
>> >>
>> >> There's a "Backlog" custom field that's enabled on a few projects for
>> >> this purpose.
>> >>
>> >> I don't think the two are equivalent though. For instance, I wouldn't
>> >> want to see a design task added in Redmine. I think stories often
break
>> >> down into more tasks and individual tickets, so represent a higher
level
>> >> description or goal.
>> >
>> > Can we modify values of the field Tracker? Current values are "Bug,
>> > Feature, Support, Refactor".I can see adding "Design" there as a way
to go.
>>
>> Yes, we can add new tracker types. It's possible to change which fields
>> are used on each type of tracker.
>>
>> –
>> Dominic Cleal
>> Red Hat Engineering
>>
>> –
>> You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
> –
> You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
···
On Aug 13, 2013 4:47 PM, "Dmitri Dolguikh" wrote:
> On Tue, Aug 13, 2013 at 2:08 PM, Dominic Cleal wrote:
>> On 13/08/13 13:54, Tomas Strachota wrote:
>> > On 08/13/2013 02:36 PM, Dominic Cleal wrote:
>> >> On 13/08/13 13:25, Dmitri Dolguikh wrote:
> For more options, visit https://groups.google.com/groups/opt_out.
I don't see any value in using Trello for a single column - it's usefulness
is directly related to Kanban-style drag'n'drop of cards between states
(just as you would with Post-Its on a physical Kanban board). If we are
proposing such a system, then I'm not sure I see the point of Trello - a
single list could be maintained almost anywhere (such as the original
etherpad backlog - not that I'm suggesting we go back to that).
If the plan is to add more detail to the backlog board on Trello, such as a
separate To-Be-Groomed column, or columns per type of work (currently we
have a lot of cards for RBAC, for example, which could be a column) then
Trello (or Kanban in general, thinking about that Redmine plugin) retains
some usefulness.
···
On 13 August 2013 14:47, Dmitri Dolguikh wrote:
I think it’s possible to switch to Redmine exclusively; I think we
wouldn’t need to introduce additional/custom fields - what I currently see
in Redmine should suffice. In some ways it would even be an improvement -
searching/filtering in Redmine is significantly better compared to Trello,
for example. Redmine lacks a clean way to create parent story - children
tasks associations though, which may become a hassle very quickly.
Dominic - we could use Trello for backlog and backlog grooming only, and
switch to Redmine for any work being allocated for/performed during sprint:
we’d move stories from Trello to Redmine during sprint planning. Is
everybody ok with this approach?
> I think it's possible to switch to Redmine exclusively; I think we
> wouldn't need to introduce additional/custom fields - what I currently
> see in Redmine should suffice. In some ways it would even be an
> improvement - searching/filtering in Redmine is significantly better
> compared to Trello, for example. Redmine lacks a clean way to create
> parent story - children tasks associations though, which may become a
> hassle very quickly.
>
> Dominic - we could use Trello for backlog and backlog grooming only,
> and switch to Redmine for any work being allocated for/performed
> during sprint: we'd move stories from Trello to Redmine during sprint
> planning. Is everybody ok with this approach?
>
> -d
>
+1
···
On 08/13/2013 03:47 PM, Dmitri Dolguikh wrote:
>
> On Tue, Aug 13, 2013 at 2:08 PM, Dominic Cleal > wrote:
>
> On 13/08/13 13:54, Tomas Strachota wrote:
> > On 08/13/2013 02:36 PM, Dominic Cleal wrote:
> >> On 13/08/13 13:25, Dmitri Dolguikh wrote:
> >>> Foreman core and smart-proxy projects both have a policy of
> having a
> >>> Redmine ticket for each PR (new projects are likely to adopt
> the same
> >>> policy). As we are using Trello for planning and keeping track of
> >>> progress during sprints, at least some of this information
> needs to be
> >>> present there as well.
> >>>
> >>> In an attempt to reduce duplication and the number of places where
> >>> information is located, I propose to phase out Trello and
> switch to
> >>> Redmine exclusively for all bug- and story-tracking needs.
> >>>
> >>> Thoughts?
> >>
> >> There's a "Backlog" custom field that's enabled on a few
> projects for
> >> this purpose.
> >>
> >> I don't think the two are equivalent though. For instance, I
> wouldn't
> >> want to see a design task added in Redmine. I think stories
> often break
> >> down into more tasks and individual tickets, so represent a
> higher level
> >> description or goal.
> >
> > Can we modify values of the field Tracker? Current values are "Bug,
> > Feature, Support, Refactor".I can see adding "Design" there as a
> way to go.
>
> Yes, we can add new tracker types. It's possible to change which
> fields
> are used on each type of tracker.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google
> Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to foreman-dev+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
What about either of the following:
https://github.com/cprice-puppet/redmine-trello - This project
provides extremely simplistic synchronization of Redmine tickets and
github pull requests to Trello boards.
https://github.com/netaustin/redmine_task_board - A Redmine plugin
which creates Kanban-style drag and drop taskboards per project.
···
On Tue, Aug 13, 2013 at 4:27 PM, Ohad Levy wrote:
>
> On Aug 13, 2013 4:47 PM, "Dmitri Dolguikh" wrote:
>>
>> I think it's possible to switch to Redmine exclusively; I think we
>> wouldn't need to introduce additional/custom fields - what I currently see
>> in Redmine should suffice. In some ways it would even be an improvement -
>> searching/filtering in Redmine is significantly better compared to Trello,
>> for example. Redmine lacks a clean way to create parent story - children
>> tasks associations though, which may become a hassle very quickly.
>>
>> Dominic - we could use Trello for backlog and backlog grooming only, and
>> switch to Redmine for any work being allocated for/performed during sprint:
>> we'd move stories from Trello to Redmine during sprint planning. Is
>> everybody ok with this approach?
> +1
>
>>
>> -d
>>
>>
>> On Tue, Aug 13, 2013 at 2:08 PM, Dominic Cleal wrote:
>>>
>>> On 13/08/13 13:54, Tomas Strachota wrote:
>>> > On 08/13/2013 02:36 PM, Dominic Cleal wrote:
>>> >> On 13/08/13 13:25, Dmitri Dolguikh wrote:
>>> >>> Foreman core and smart-proxy projects both have a policy of having a
>>> >>> Redmine ticket for each PR (new projects are likely to adopt the same
>>> >>> policy). As we are using Trello for planning and keeping track of
>>> >>> progress during sprints, at least some of this information needs to
>>> >>> be
>>> >>> present there as well.
>>> >>>
>>> >>> In an attempt to reduce duplication and the number of places where
>>> >>> information is located, I propose to phase out Trello and switch to
>>> >>> Redmine exclusively for all bug- and story-tracking needs.
>>> >>>
>>> >>> Thoughts?
>>> >>
>>> >> There's a "Backlog" custom field that's enabled on a few projects for
>>> >> this purpose.
>>> >>
>>> >> I don't think the two are equivalent though. For instance, I wouldn't
>>> >> want to see a design task added in Redmine. I think stories often
>>> >> break
>>> >> down into more tasks and individual tickets, so represent a higher
>>> >> level
>>> >> description or goal.
>>> >
>>> > Can we modify values of the field Tracker? Current values are "Bug,
>>> > Feature, Support, Refactor".I can see adding "Design" there as a way to
>>> > go.
>>>
>>> Yes, we can add new tracker types. It's possible to change which fields
>>> are used on each type of tracker.
>>>
>>> --
>>> Dominic Cleal
>>> Red Hat Engineering
