infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-17247) [GitHub] non-committer is able to change issue assignment
Date Sun, 02 Dec 2018 19:04:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-17247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus resolved INFRA-17247.
-------------------------------------
    Resolution: Fixed

Github stated:

It looks like the user's permissions to the repository were removed previously, but the un-assignment
of their user from Issues didn't fully complete.

When kalyc added a comment to the Issue, the permissions logic was triggered and the user
was un-assigned. This is incorrectly being attributed to kalyc because the comment is the
event that triggered the un-assignment.

This isn't expected behaviour and we've escalated to our Engineering Team for further investigation.

---


If I hear anything more back I'll post it to this ticket, but I am otherwise closing it as
it is not something Infra can do anything about.

> [GitHub] non-committer is able to change issue assignment
> ---------------------------------------------------------
>
>                 Key: INFRA-17247
>                 URL: https://issues.apache.org/jira/browse/INFRA-17247
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Github
>            Reporter: Marco de Abreu
>            Assignee: Chris Lambertus
>            Priority: Major
>
> In https://github.com/apache/incubator-mxnet/issues/7247 we have the case that a non-committer
was able to unassign an issue although we were under the impression that they should not have
the permission.
> For some context: We operate a bot in the mxnet repository (mxnet-label-bot) that operates
with my credentials. It's purpose is to only add and remove labels - it doesn't even support
issue assignment at all. We thought that it might have been a malfunction, but that would
have showed up under my name instead of kalyc. 
> Could you help us to track this issue down?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message