[#MYAA-11] As System, I may manage any Custom Permission, not only Minyaa Permissions - Minyaa JIRA

Allow ExtendedSchemePermissions to manage Permission defined in orther Plugins

This issue is caused by:
MYAA-299	ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission
MYAA-340	In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown
MYAA-409	Build of Minyaa for JIRA 3.x was not well done with Java 1.4
MYAA-359	When ExtendedDeleteIssueOperation is instanciated, the default DeleteIssueOperation is systematically disable. The Plugin cache is reset systematically too
MYAA-296	Edit Screen for default com.atlassian.jira.workflow.condition.PermissionCondition allows to select Auto Transition permission but View Screen fails in display. Edit no more available
MYAA-420	In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException

This issue is related to:
MYAA-299	ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission
MYAA-296	Edit Screen for default com.atlassian.jira.workflow.condition.PermissionCondition allows to select Auto Transition permission but View Screen fails in display. Edit no more available
MYAA-409	Build of Minyaa for JIRA 3.x was not well done with Java 1.4
MYAA-335	Users without Edit Permission have access to the Time Spent tab panel
MYAA-340	In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown
MYAA-278	Uninstalling minyaa doesnt restore entityengine.xml.myaa and entitygroup.xml.myaa
MYAA-359	When ExtendedDeleteIssueOperation is instanciated, the default DeleteIssueOperation is systematically disable. The Plugin cache is reset systematically too
MYAA-420	In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException

There are no comments yet on this issue.

Vote (0)

Watch (0)

Minyaa Suite