I've deleted the the "Team AL-GTD - 1" version that somebody had added
to the Foreman project in Redmine, as it's project-wide and so is set on
every issue.
Hello
Could you please elaborate a bit why this is considered bad? I planned to use
the same for planning and prioritization of our issues too. What do you mean
by "set on every issue"? As far as I can tell when I create new global
version, a new field "Target version" appears on issue form but it's not
mandatory to fill so people can ignore it. Note that version does not conflict
with releases that I know are being used actively.
If we agree on not using versions for this purpose, would everyone be OK with
adding few custom fields for all projects?
Thank you
···
On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote: > I've deleted the the "Team AL-GTD - 1" version that somebody had added > to the Foreman project in Redmine, as it's project-wide and so is set on > every issue.–
Marek
>> I've deleted the the "Team AL-GTD - 1" version that somebody had added
>> to the Foreman project in Redmine, as it's project-wide and so is set on
>> every issue.
>
> Hello
>
> Could you please elaborate a bit why this is considered bad? I planned to use
> the same for planning and prioritization of our issues too. What do you mean
> by "set on every issue"? As far as I can tell when I create new global
> version, a new field "Target version" appears on issue form but it's not
> mandatory to fill so people can ignore it.
Currently prprocessor's configured to set the target version to the
first available automatically, so a PR is opened and it's set to the
upcoming target version. Issues in the Foreman project were being set to
this "Team AL-GTD 1" when it was created.
Perhaps the prprocessor behaviour can be changed to be configurable per
project if other projects are relying on this feature.
> Note that version does not conflict
> with releases that I know are being used actively.
Yes, in Foreman we're using releases, but other projects may use the
target version.
···
On 27/07/16 08:54, Marek Hulán wrote: > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:–
Dominic Cleal
dominic@cleal.org
> >> I've deleted the the "Team AL-GTD - 1" version that somebody had added
> >> to the Foreman project in Redmine, as it's project-wide and so is set on
> >> every issue.
> >
> > Hello
> >
> > Could you please elaborate a bit why this is considered bad? I planned to
> > use the same for planning and prioritization of our issues too. What do
> > you mean by "set on every issue"? As far as I can tell when I create new
> > global version, a new field "Target version" appears on issue form but
> > it's not mandatory to fill so people can ignore it.
>
> Currently prprocessor's configured to set the target version to the
> first available automatically, so a PR is opened and it's set to the
> upcoming target version. Issues in the Foreman project were being set to
> this "Team AL-GTD 1" when it was created.
>
> Perhaps the prprocessor behaviour can be changed to be configurable per
> project if other projects are relying on this feature.
Ah, makes sense now, thanks. So unless anyone objects (see below) I'd send a
patch to PR processor to ignore target version.
> > Note that version does not conflict
> > with releases that I know are being used actively.
>
> Yes, in Foreman we're using releases, but other projects may use the
> target version.
I went through projects and it seems it's mostly used by Discovery Hammer and
OpenSCAP. Others seems to me to be obsolete or some testing versions. For our
planning purpose the version does not have to be even shared with subprojects
so plugins can continue using it while they would not see our global version.
The only downside is that we don't see the plugin issue in product backlog if
it's target version is already set to some specific plugin version. That should
be fine in our use case.
So is there any concern from anyone using redmine for his or her plugin
regarding adding few Foreman-wide versions? If not I hope to start using it
from tomorrow (after pr processor is updated of course).
Thank you
···
On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote: > On 27/07/16 08:54, Marek Hulán wrote: > > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:–
Marek
>> >> I've deleted the the "Team AL-GTD - 1" version that somebody had added
>> >> to the Foreman project in Redmine, as it's project-wide and so is set on
>> >> every issue.
>> >
>> > Hello
>> >
>> > Could you please elaborate a bit why this is considered bad? I planned to
>> > use the same for planning and prioritization of our issues too. What do
>> > you mean by "set on every issue"? As far as I can tell when I create new
>> > global version, a new field "Target version" appears on issue form but
>> > it's not mandatory to fill so people can ignore it.
>>
>> Currently prprocessor's configured to set the target version to the
>> first available automatically, so a PR is opened and it's set to the
>> upcoming target version. Issues in the Foreman project were being set to
>> this "Team AL-GTD 1" when it was created.
>>
>> Perhaps the prprocessor behaviour can be changed to be configurable per
>> project if other projects are relying on this feature.
>
> Ah, makes sense now, thanks. So unless anyone objects (see below) I'd send a
> patch to PR processor to ignore target version.
>
>> > Note that version does not conflict
>> > with releases that I know are being used actively.
>>
>> Yes, in Foreman we're using releases, but other projects may use the
>> target version.
>
> I went through projects and it seems it's mostly used by Discovery Hammer and
> OpenSCAP. Others seems to me to be obsolete or some testing versions. For our
> planning purpose the version does not have to be even shared with subprojects
> so plugins can continue using it while they would not see our global version.
> The only downside is that we don't see the plugin issue in product backlog if
> it's target version is already set to some specific plugin version. That should
> be fine in our use case.
>
> So is there any concern from anyone using redmine for his or her plugin
> regarding adding few Foreman-wide versions? If not I hope to start using it
> from tomorrow (after pr processor is updated of course).
+1, I want to start using it the same way as well.
– Ivan
···
On Wed, Jul 27, 2016 at 11:08 AM, Marek Hulán wrote: > On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote: >> On 27/07/16 08:54, Marek Hulán wrote: >> > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:Thank you
–
Marek–
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/d/optout.
I guess this should be enough to allow us staring using the backlogs
plugin again
https://github.com/theforeman/prprocessor/pull/48
– Ivan