Can I set up JIRA so that a third party can only view specific tickets?

We occasionally outsource some of our development work to third party development teams.  We would like to have a flag/dropdown/tag to mark it as a "xyz company" ticket, and then restrict their view so that they can only see tickets that have been flagged for them.  

We still want these tickets to stay on the same board, and to be seen by our own internal developers.  

Is this possible?

2 answers

0 votes

The easiest way is creating a new project for that third party's issues, modifying the board's filter to include issues of the new project as well.

We may have tickets that start out being assigned to one of our developers, then get sent out to be completed, then come back to us for QA or UAT.  We already use multiple projects, so if at all possible, I would really like to be able to keep this project all on one board so it can stay organized.  

There are also other alternative ways based on Security Levels, but that approach would require much more steps for achieving what you need.

Note that one board can show issues from any number of projects.

Ok, I am at least a little closer.  

In issue security, I set the view so that the following groups can view the tickets 

  • Current assignee
  • Group (Internal Developers)
  • Group (Internal Managers)
  • Reporter

This way, the person who reported the ticket can see it, all internal Developers and Managers can see it, and anyone can see a ticket that is assigned to them.  

Our game plan is to assign the tickets to the third party manager, and let him/her reassign them to his/her team members as they see fit.  We can still track their progress internally.

During testing, this seems to work with any new tickets I create... however the tickets created prior to the rule being implemented are still visible to everyone.  

If I switch back to "None", I get the following message...

None (3 affected Issues)Security on these issues will be removed

And it removes all security

If I try to switch back to the Issue Security Scheme I created, I get the following message

"There are no previous secured issues."


Is there any way to secure tickets that were previously set to "none"


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

369 views 6 0
Join discussion

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