- changed status to open
Scheduled Issues not accepting the default Issue Security settings
Hello,
I have some projects set with default issue security. However, when they issues are scheduled, it loses this setting. Important issue as I cant have secure issues not being secured.
Thanks!
Comments (6)
-
-
reporter Hi,
I am using Version: 3.2.13 of TSP. JIRA 6.4.10.
What i mean is that in a project you can define "issue security". So for example, i have a DEFAULT issue security policy for a project that states that "only the reporter and admins can view an issue" I noticed that for autogenerated scheduled issued, tihs policy is not being applied. So that ANYONE (not just admins, reporters) can view the issues. Therefore, it appears that issue security is not being applied to scheduled issues.
Does that make sense?
Thanks
-
Hi Kevin,
Sorry for late answer. You are right, I had just reproduced this problem. The default security level is ignored. We will fix this and release updated plugin for JIRA 6.3 - 6.4.*.
However there's workaround for this issue. The Scheduler Plugin ignore security level field because this field is not presented in creation form. So, for now please to add this field to issue creation screen.
Will keep you updated.
-
Hi Kevin,
In newly released version 3.2.15 we included patch for this issue, so from now every new issue without issue security level set, will automatically have projects default security level. Please upgrade to new version from out bitbuckets download section.
Best regards.
-
- changed status to resolved
-
- changed status to closed
- Log in to comment
Hello Kevin,
We need some more information to support you. Could you please write which version of TSP are you using? In the newest versions of our plugin the permissions are much more restricted and subject to the will of administrators. Would you describe your problem more broadly? Specifically, what do you mean by "secure issues not being secured"? Do you mean that users can workaround some permissions and are able to create those issues?
Regards, Jacek Ostrowski