Re: How to close migrated issues without a merge?

[chuck c <bubbasnmp () gmail com>]

I finally got around to checking how many I had open and was shocked to see
2% of all open issues were me.
So I'm in fix it or close it mode.
Just occurred to me recently that I can have my own messy issues list on my
Wireshark mirror. :-)

On Mon, Oct 26, 2020 at 7:53 PM John Thacker <johnthacker () gmail com> wrote:

> My understanding is that people have to be made members at the "Reporter"
> level or higher in order to close issues (which is moving issues to the
> Closed list) or otherwise manage them (label, etc.)
>
> https://docs.gitlab.com/ee/user/project/issue_board.html#permissions
>
> https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions
>
> Since the project doesn't have people with Reporter level membership, it's
> really just the core team members that can close issues.
> (Effectively, merging gates them the same way since the core team must
> approve merges.)
>
> Here's another obvious example that should be closed, regarding Bugzilla
> and MIME types of files:
> https://gitlab.com/wireshark/wireshark/-/issues/8476
>
> John
>
> On Mon, Oct 26, 2020, 8:26 PM chuck c <bubbasnmp () gmail com> wrote:
>
> > Example closed with a merge:
> > https://gitlab.com/wireshark/wireshark/-/issues/16000
> >  Opened 1 year ago by Wireshark GitLab MigrationGuest
> > AndersBroman @AndersBroman closed via merge request !718 (merged) 15
> > hours ago
> >
> > No code to merge. Doing housekeeping.
> > https://gitlab.com/wireshark/wireshark/-/issues/16347
> > Opened 9 months ago by Wireshark GitLab MigrationGuest
> >
> > Added a comment showing the fix but can't close the issue.
> > Is there a way to assign issues back to the person that opened it on
> > bugziila?
> >
> > ___________________________________________________________________________
> > Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> > Archives:    https://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> >              mailto:wireshark-dev-request () wireshark org
> > ?subject=unsubscribe
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe