JIRA permission setting problem

[Xiangdong Huang <sa...@gmail.com>]

Hi,

When I wrote the podling report, I reviewed all the JIRA issues of IoTDB
again, and find that the status of many issues is incorrect...

Now one problem is:

First, a developer can not mark an issue as "in progress", "resolved" and
can not assign the issue to himself (or other persons), if the issue is not
reported by the developer.

Second, if I report an issue, I just can mark the issue as resolved or
closed. Assigning the issue to someone or mark it as "in progress" is
forbidden.

Third, some developers (e.g., @Qingxin Feng) say that they even can not
mark an issue as resolved even though the issue is reported by themselves.

I think it is better that if developers can have some privilege to operate
the status of the issue. If we want to avoid freshman mis-operates the
issues, we can deal a rule about how and when to change the status of an
issue.

NEED mentors' help [1]. :D

Best,

[1] https://issues.apache.org/jira/browse/INFRA-18568?filter=-2
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

Re: JIRA permission setting problem

[Willem Jiang <wi...@gmail.com>]

Hi，

I think I hide this kind of issue in ServiceComb JIRA as the
contributor doesn't has the right to resolve or assign the JIRA issue
any more.
I manage to resolve the issue by adding the user into committer group.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 5, 2019 at 1:30 PM Xiangdong Huang <sa...@gmail.com> wrote:
>
> Hi,
>
> When I wrote the podling report, I reviewed all the JIRA issues of IoTDB
> again, and find that the status of many issues is incorrect...
>
> Now one problem is:
>
> First, a developer can not mark an issue as "in progress", "resolved" and
> can not assign the issue to himself (or other persons), if the issue is not
> reported by the developer.
>
> Second, if I report an issue, I just can mark the issue as resolved or
> closed. Assigning the issue to someone or mark it as "in progress" is
> forbidden.
>
> Third, some developers (e.g., @Qingxin Feng) say that they even can not
> mark an issue as resolved even though the issue is reported by themselves.
>
> I think it is better that if developers can have some privilege to operate
> the status of the issue. If we want to avoid freshman mis-operates the
> issues, we can deal a rule about how and when to change the status of an
> issue.
>
> NEED mentors' help [1]. :D
>
> Best,
>
> [1] https://issues.apache.org/jira/browse/INFRA-18568?filter=-2
> -----------------------------------
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院