Hi,
I have these workflows
I created a developper group with multiple users.
I would like that only users on developper group have a visibility on OSBL&OSQ issue type.
I have seen that some posts say that this is not possible, but they are old publications. Maybe is it possible today.
I have few clues with Issue Security Scheme and post function but I do not know how can I do ...
It would be great if someone can help me !!
Kind regards
It's not *directly* possible, never has been, and that's not changed.
You can't say "you can only see issue typ X in a project".
What you can do is use issue security in a structured way. The basic setup for a simple case like yours is:
Your users will still know OSBL and OSQ are there. They will be able to create them. But only the developers will be able to see them. It's not quite "issue type security" really, but it behaves pretty close to it
Thanks Nic,
I will follow your advice and I hope it will work :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great, it works !!!
I have a last question :
Only new issues created are affected by this change, I am right ??. So if I want to update all the old issues concerned, can I easily do it or I must create a groovy script.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct.
You should be able to search for all the old issues and use "bulk edit" to set the level on them.
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.
Thank you all,
Nic, when you say "In workflow A, add a post-function that sets the security level to "secured"", on which transtion I apply this post function ??
On the first transition "Create" ?? If I do that the users will still able to create issue but only developer group can see them
This is my workflow
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can apply it on any transition you want. Most would put it on Create because they want to hide the issue for its whole lifecycle, but for your workflow, I would consider doing it on activate. The users would then see that they've created an issue and everyone can see it, but as soon as you activate it, it would disappear from their lists. You'll be able to explain "triage means we remove it from view" more easily.
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.
Just to re-iterate what has been said this a very similar feature request has been closed as a "Won't fix" some time ago at JRASERVER-5865. Beyond that I would follow Nic's recommendations and go from there!
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This desire has been around before I started working with JIRA in 2007 so I expect it will never be changed. Nic's solution is as good as it gets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Joe
2007 ... I started working with JIRA since ... May 2017 :)
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.