Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How about syntax and usage of status properties in workflows?

Stefan Nahr November 6, 2019

Hello there,

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)

  1. Does anybody know about how we can use attributes of the class ProjectPermissions here?
  2.  jira.projectpermissions brings up an errormessage, jira.permission.move_issued.denied doesn't.
    Why the syntaxcheck of the filledin attributes seems incomplete?
  3. 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

0 votes
Stefan Nahr November 20, 2019

After 1 week still no reponse so I opened a support ticket. Closed here

Suggest an answer

Log in or Sign up to answer