We've disabled the possibility to clone tasks in certain projects using customized workflows. Namely, each workflow step has an additional property of jira.permission.create.clone = disable. In projects influenced by this setting, Quick Subtasks plugin does not work (no GUI option to create multiple subtasks, error when trying to make things work manually -> /rest/subtasks-create/1.0/facility/issue/XXX-1).
The error is "Unknown type 'clone' in meta attribute 'jira.permission.create.clone'. Valid permission types are defined in permission-types.xml"
This type of bug has already been described here: https://jira.atlassian.com/browse/JRA-59487
Although it's understandable that using parameters as above is not the most kosher way to do things, we find it to be the best way to tailor workflow to our needs.
Please advise - the goal would be to keep current workflows' setting and make Quick Subtasks usable again. Is it possible to make proper changes in Quick Subtasks?
JIRA Server v7.1.7, Quick Subtasks 4.3.0
@Rafal Szybko Tbh .. I have never heard of this setting before and therefore I need to investigate. I have added a new feature request to the project's issue tracker here, please feel free to comment/watch:
https://bitbucket.org/hascode/jira-quick-subtasks/issues/288/allow-compatibility-with-createclone
@Micha Kops All right, thank you. Will keep a vigilant eye on that Bitbucket issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm sorry to say that there is no progress yet.
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.