restrict visibility by issue type


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

5 answers

3 votes

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:

  • Create an issue security scheme that has one level of something like "secured"
  • Set secured so that it says "Developer group only"
  • Create two workflows (Let's say A and B)
  • In workflow A, add a post-function that sets the security level to "secured"
  • Create a workflow scheme that says
  • For issue types OSBL and OSQ, use workflow A
  • For all others use workflow B
  • If you wish to keep this 100% automatic, go through all the screens the project uses for all issues and remove the "security level" field from them all so users can't change it.

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 :)


0 votes
Joseph Pitt Community Champion Jun 23, 2017

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.  

Thanks Joe

2007 ... I started working with JIRA since ... May 2017 :)

0 votes

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!



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 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.

ok, thanks again Nic !!

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.



You should be able to search for all the old issues and use "bulk edit" to set the level on them.

Ok Nick, I will try with "bulk edit"


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,664 views 18 21
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you