i've already set up permissions to only allow issue linking, which brings "is a cloner of / is cloned by" to developers role
so far so good.
the issue can still be cloned just by selecting "Clone" from the More Actions tab
this is really annoying cause some users here are way too lazy to create a new issue from scratch...they simply clone a resolved one...
You can't do it on a project by project basis unless you do some coding. i.e. add a condition to the respective web-item in system-issueoperations-plugin.xml.
Or maybe disable the system plugin and define an isue operation in your plugin along with the condition. You can make use of existing classes and jsp files.
Yes, on a download instance, the administrator can disable the shipped clone operation following the instructions.You only need the plugin if you want to replace it with clone operations can be restricted or customized on a project by project basis if that is your need.
We have similar issues with cloning In a couple of projects. Users clone an issue, but then do not have edit permissions to modify key details. We have good reasons for not granting edit permissions in those projects and we expect our users to "remember" that they should not clone in those projects.
I understand that clone would not be permitted if we remove the "create issues" permission, but we do want our users to be able to create new issues in those projects.
Would it be possible to make the "clone" action depend on both "create issues" and "edit issues" permissions?
That would solve most of our problem with regards to cloning.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG