The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
we want to protect issues in status "Done" from being moved to other projects. We found some interesting approaches on this site: j-tricks.com - Permissions based on workflow-status BUT looking forward on the mentioned class Permissions on Atlassian.serurity.Permissions we found them marked as deprecated, so we took a look at the recommended class ProjectPermissons. How can we enter these permissions (from class ProjectPermissions) at the status-property-window? jira.permission.move_issue.denied would work but is deprecated jira.projectpermissions.move_issues.denied leads to an error, because jira.projectpermissions seems to be unknown here. jira.permissions.move_issues.denied is accepted and seems to work. jira.permission.move_issued.denied is also accepted (without errormessage) but we haven't tested, how JIRA will work with this attribute (yes, it's an unknown/misspelled attribute)
Does anybody know about how we can use attributes of the class ProjectPermissions here?
jira.projectpermissions brings up an errormessage, jira.permission.move_issued.denied doesn't. Why the syntaxcheck of the filledin attributes seems incomplete?
At Atlassian workflow-properties Atlassian notes, that "Not everything on this page is recommended!" Does anybody know, what exactly isn't respectively is recommended here?
Thanks in advance for your replies
1 answer
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.