New issue
 Projects > website > Issues > Feature #2891

Should limit the permission when a developer create an issue

Feature #2891 [Closed]
zhangxm 2013-10-08 02:13 . Updated over 9 years ago

When a developer create an issue, he/she should not be able to
* edit Target version, it should be Unplanned
* edit Assignee

eva 2013-10-15 07:40
  • Due date set to 2013-10-14
  • Status changed from New to Resolved
  • % Done changed from 0 to 100 2013-10-15 07:44

Walzer update:
* The target is that, prevent this thing to happen again Many newbies create issues to ask their “how to use” questions, assign to core developer with an “urgent” priority.
* So, when non-member creates an issue, this issue
*** can’t be assigned to anyone
*** has only “low” priority
** can’t have target version, even in “unplanned” is not allowed. We will review these issues periodically.

eva 2013-10-16 03:31

1 limit non-member user permission when create new issue.
2 set issues color by priority(high:green, urgent:yellow, immediate:red)
3 if you want to filter issues by blank target version, you may set target version filter as “none” 2014-01-25 13:05
  • Status changed from Resolved to Closed

Atom PDF

Start date:2013-10-08
Due date:2013-10-14
% Done:


Target version:-