Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Limit information on view screen for some projectroles

Hi, I have a workflow with where the reporter gives many information and out of this several subtasks are created.


When a subtask is created there is also an email sent to the people in the department that is responsible for the subtask.


I achieved both with Scriptrunner. Custom E-Mail and Create Sub-Task.


Some of the information are not for the eyes of others. So I want them to be hidden in the view screen.


As far as I know that is not possible without fancy javascripts or additonal plugins.


So maybe my concept is not the best.


What would you do to give the people just the information that they need and don't get a look onto other customfields?



1 answer

Hi @Lars Swart ,

First I would check how confidential the information is. Because if it isn't confidential, you could just put the fields in different tabs on the screens (i.e. Project Lead, Worker, QA, ...). And it's usual a good thing if people can look everything up. This is in some ways exactly the idea behind a ticketing system.

But there are use cases where information shouldn't be available so let's assume your use case is one of them. Then I would work with an issue security scheme and set the issue security level in the create transition depending on the issue type. If you need different kind of sub-tasks, you'll need to do this for every workflow independently.

Jira is in general designed to be very open on project level, to enable team collaboration. That's why it will take some configuration time there to enable such a restrictive workflow

Hi Mario,

yeah thats what I thought. Thats a complexity level I wouldnt go for. 


But you brought an interesting thing up. I use different tabs. Is it possible to hide whole tabs in the view screen? 

Not with Scriptrunner afaik.

I am pretty sure you need a JavaScript hack to hide things in the detail view (even the tabs).

I guess you need to some javascript hiding and check every version that the classes are the same or install something like and check every upgrade if this still works.

Or you could alter your approach to create linked tasks in other projects where only the people have access, who are allowed to see the issue.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events