Bug 205431 - Duplicate CC/maintainer-feedback/Assignee created when Reporter sets (correctly) them during issue creation
Summary: Duplicate CC/maintainer-feedback/Assignee created when Reporter sets (correct...
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords: easy, needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2015-12-19 11:24 UTC by Kubilay Kocak
Modified: 2022-12-19 06:33 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kubilay Kocak freebsd_committer freebsd_triage 2015-12-19 11:24:03 UTC 
When the Reporter of an issue sets the CC, Assignee and maintainer-feedback flags field during initial issue creation, Auto-Assigner creates duplicate CC, maintainer-feedback flag and Assignee attributes:

            Bug ID: 205429
           Summary: news/xpn : add tray icon
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: nivit@FreeBSD.org
          Reporter: rainbow@irh.it
                CC: nivit@FreeBSD.org
                CC: nivit@FreeBSD.org
             Flags: maintainer-feedback?(nivit@FreeBSD.org),
                    maintainer-feedback?(nivit@FreeBSD.org)
          Assignee: nivit@FreeBSD.org

The duplicate CC and Assignee attributes don't seem to cause problems (since it can only be added once), other than the duplicate attributes listed in the initial issue email, but with the maintainer-feedback flag, two instances are created with the same values
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2015-12-19 11:30:56 UTC 
Add another example of an issue where category/port was *not* put in Summary, but Assignee and maintainer-feedback was correctly added, resulting in:

            Bug ID: 205430
           Summary: minidlna server not visible in network
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
---->     Assignee: wg@FreeBSD.org
          Reporter: pvoigt@uos.de
---->     Assignee: wg@FreeBSD.org
             Flags: maintainer-feedback?(wg@FreeBSD.org)
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2015-12-21 14:04:55 UTC 
Another example is bug 205437:

The Reporter set CC fields (correctly) on initial issue creation, resulting in:

            Bug ID: 205437
           Summary: [PATCH] net/rubygem-bunny: update to 2.2.2 &
                    net/rubygem-amq-protocol to 2.0.1
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: dch@skunkwerks.at
                CC: renchap@cocoa-x.com, sunpoet@FreeBSD.org
                CC: renchap@cocoa-x.com, sunpoet@FreeBSD.org
          Keywords: patch

In this case 2 x maintainer-feedback flags were not added and set to ? <maintainer-email> for the two ports referenced in the Summary
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2015-12-21 14:06:01 UTC 
Also note again in comment 2, the duplicate CC