jira.i18n.title
jira.issue.editable
jira.permission.*
Hello @Pramodh M ,
I just did a quick test and the workflow properties were working without issue in my tests.
I tested with both 'jira.issue.editable = false' and 'jira.permission.work.denied = denied" where both options are successfully applied to the workflow and working without issue in the new issue view:
The number one thing I would suggest verifying is that the workflow successfully had the draft published after the properties were set as the Properties require navigating back to the previous workflow edit screen to apply the changes, as there is not a publish option on the workflow property configuration screen. This is the most common issue relating to workflow property configuration issues.
If the draft is verified as published and still not working, what are the configurations you are using in your workflow for the properties for each of the above-noted properties that are failing? Additionally please note where are the properties placed in the workflow (i.e. in the transitions or the statuses)? I can take a look to see if we can identify the issue.
Regards,
Earl
Thanks for the reply!
I have raised the Support ticket Here
Yes, I have Published and it is for Status and not transition as it is a Step Property
One thing, 'jira.issue.editable = false' is not completely working
Please check even when we have the above property set, we can edit the Assignee field and any other custom fields that are there in Details Panel.
Please see the details below
Also, Can you please make sure other permissions like edit is also working. I had it in tested in my instance for edit permission and it's ignoring that property
Thanks,
Pramodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Pramodh M ,
I'm just relaying the info that you received in the support request from @Tulsi to this thread, in case anyone else finds this with a similar issue.
Primarily the jira.i18n.submit & jira.i18n.title are not currently supported on the Cloud and we are tracking interest here:
Next, there are a few Bugs that are not reflected properly in the documentation and we have the following Documentation update request in place tracking the updates:
The noted Bugs that apply are:
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.