Because Katello is a nested project under Foreman in Redmine, we can only
see Foreman versions in the "version" field. It would be great to have a
custom text box field "Found In Version" that bug reporters can provide the
exact RPM they installed to see the issue.
Let me know if you would find this useful.
···
--
Andrew Kofink
akofink@redhat.com
IRC: akofink
Associate Software Engineer
Red Hat Satellite
If we do this, we should clarify that the current "version" field is used
for releases by calling it "target version" or something similar.
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
···
On Mon, Oct 16, 2017 at 10:18 AM, Andrew Kofink wrote:
RFC:
Because Katello is a nested project under Foreman in Redmine, we can only
see Foreman versions in the “version” field. It would be great to have a
custom text box field “Found In Version” that bug reporters can provide the
exact RPM they installed to see the issue.
Let me know if you would find this useful.
–
Andrew Kofink akofink@redhat.com
IRC: akofink
Associate Software Engineer
Red Hat Satellite
Foreman has this,
but I'm not sure we can rename the Release field since it's part of the
Redmine Backlogs plugin though my memory is fuzzy here. I think someone
with admin rights on Redmine can say more about the practicalities but
the idea makes a lot of sense to me.
···
On Mon, Oct 16, 2017 at 01:38:18PM -0400, John Mitsch wrote:
>+1
>
>If we do this, we should clarify that the current "version" field is used
>for releases by calling it "target version" or something similar.
>
>John Mitsch
>Red Hat Engineering
>(860)-967-7285
>irc: jomitsch
>
>On Mon, Oct 16, 2017 at 10:18 AM, Andrew Kofink wrote:
>
>> RFC:
>>
>> Because Katello is a nested project under Foreman in Redmine, we can only
>> see Foreman versions in the "version" field. It would be great to have a
>> custom text box field "Found In Version" that bug reporters can provide the
>> exact RPM they installed to see the issue.
>>
>> Let me know if you would find this useful.
Perhaps using a template for new issues. Here is an example from github:
[provide a description of the issue]
Version
[provide output of the openshift version or oc version command]
Steps To Reproduce
[step 1]
[step 2]
Current Result
Expected Result
Additional Information
[try to run $ oc adm diagnostics (or oadm diagnostics) command if
possible]
[if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5]
[consider attaching output of the $ oc get all -o json -n <namespace>
command to the issue]
[visit https://docs.openshift.org/latest/welcome/index.html]
···
On Mon, Oct 16, 2017 at 1:47 PM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote:
https://projects.theforeman.org/projects/foreman/issues/new has this, but
I’m not sure we can rename the Release field since it’s part of the Redmine
Backlogs plugin though my memory is fuzzy here. I think someone with admin
rights on Redmine can say more about the practicalities but the idea makes
a lot of sense to me.
On Mon, Oct 16, 2017 at 01:38:18PM -0400, John Mitsch wrote:
+1
If we do this, we should clarify that the current “version” field is used
for releases by calling it “target version” or something similar.
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
On Mon, Oct 16, 2017 at 10:18 AM, Andrew Kofink akofink@redhat.com >> wrote:
RFC:
Because Katello is a nested project under Foreman in Redmine, we can only
see Foreman versions in the “version” field. It would be great to have a
custom text box field “Found In Version” that bug reporters can provide
the
exact RPM they installed to see the issue.
···
On 10/18/2017 02:55 PM, Tom McKay wrote:
> Perhaps using a template for new issues. Here is an example from github:
> https://github.com/openshift/origin/issues/new
>
> [provide a description of the issue]
>
> ##### Version
> [provide output of the `openshift version` or `oc version` command]
>
> ##### Steps To Reproduce
> 1. [step 1]
> 2. [step 2]
>
> ##### Current Result
>
> ##### Expected Result
>
> ##### Additional Information
> [try to run `$ oc adm diagnostics` (or `oadm diagnostics`) command if
> possible]
> [if you are reporting issue related to builds, provide build logs with
> `BUILD_LOGLEVEL=5`]
> [consider attaching output of the `$ oc get all -o json -n
> ` command to the issue]
> [visit https://docs.openshift.org/latest/welcome/index.html]
>
>
> On Mon, Oct 16, 2017 at 1:47 PM, Ewoud Kohl van Wijngaarden > <ewoud@kohlvanwijngaarden.nl > wrote:
>
> https://projects.theforeman.org/projects/foreman/issues/new
> has
> this, but I'm not sure we can rename the Release field since it's
> part of the Redmine Backlogs plugin though my memory is fuzzy
> here. I think someone with admin rights on Redmine can say more
> about the practicalities but the idea makes a lot of sense to me.
>
> On Mon, Oct 16, 2017 at 01:38:18PM -0400, John Mitsch wrote:
>
> +1
>
> If we do this, we should clarify that the current "version"
> field is used
> for releases by calling it "target version" or something similar.
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Mon, Oct 16, 2017 at 10:18 AM, Andrew Kofink > <akofink@redhat.com > wrote:
>
> RFC:
>
> Because Katello is a nested project under Foreman in
> Redmine, we can only
> see Foreman versions in the "version" field. It would be
> great to have a
> custom text box field "Found In Version" that bug
> reporters can provide the
> exact RPM they installed to see the issue.
>
> Let me know if you would find this useful.
>
>
> --
> 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
> .
>
>
> --
> 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.
[provide output of the openshift version or oc version command]
Steps To Reproduce
[step 1]
[step 2]
Current Result
Expected Result
Additional Information
[try to run $ oc adm diagnostics (or oadm diagnostics) command if
possible]
[if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5]
[consider attaching output of the $ oc get all -o json -n <namespace> command to the issue]
[visit https://docs.openshift.org/latest/welcome/index.html]
https://projects.theforeman.org/projects/foreman/issues/new
<https://projects.theforeman.org/projects/foreman/issues/new> has
this, but I'm not sure we can rename the Release field since it's
part of the Redmine Backlogs plugin though my memory is fuzzy
here. I think someone with admin rights on Redmine can say more
about the practicalities but the idea makes a lot of sense to me.
On Mon, Oct 16, 2017 at 01:38:18PM -0400, John Mitsch wrote:
+1
If we do this, we should clarify that the current "version"
field is used
for releases by calling it "target version" or something similar.
John Mitsch
Red Hat Engineering
(860)-967-7285 <tel:%28860%29-967-7285>
irc: jomitsch
On Mon, Oct 16, 2017 at 10:18 AM, Andrew Kofink >> <akofink@redhat.com <mailto:akofink@redhat.com>> wrote:
RFC:
Because Katello is a nested project under Foreman in
Redmine, we can only
see Foreman versions in the "version" field. It would be
great to have a
custom text box field "Found In Version" that bug
reporters can provide the
exact RPM they installed to see the issue.
Let me know if you would find this useful.
--
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
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
Nice. I'll add it to my Redmine-todo list, which I hope to get back to
shortly.
Greg
···
On Wed, 2017-10-18 at 15:00 -0400, Justin Sherrill wrote:
> I like this idea, and there seems to be a plugin already to do it: ht
> tp://www.redmine.org/plugins/redmine_issue_templates