We have Kanban boards set up for all our projects, where project managers will enter all the tasks etc. that are required to be completed. Using labels, these are then pushed into the development teams agile boards where they work through the tasks as required.
We are engaging some external developers for certain projects where we are at capacity with internal developers. I have created a single user for the contractor, and a new agile project specific to the contractor.
I want to be able to assign tasks from the project kanban boards to the contractor and in-turn they appear in the contracts board. In turn, preventing them from seeing all our other projects.
It seems, to make this work I need to edit the permission scheme and give the contractor group access to browse the project and issues, which in-turn obviously gives them visibility of the project even if they are not in entered onto the people access page.
Just wondering if anyone might have some tips on how to achieve this so the contractor can see assigned tasks in their project, from other projects without seeing the parent project?
Hi @Jeremy West
Have you looked into Security Levels in Jira
You should be able to set access for
Ask if you need more details.
@Tom Lister yeah this was my first port of call, I've not used the issue security before, gave it a shot but it did not seem to make any difference.
In theory, this would work as I could give them project access but only allow them to see assigned issues. I might have another crack.
We are currently facing the same challenge:
-we have "internal" project with all of our issues
- we have a "contractor" project with a board, containing a subset of issues from the "internal" project (filtering done via label)
How can we give access the contractors so that they can see the issues included in the "contractor" board (but do not have access to the "internal" project)?
Thanks in advance for your help
Hey @Thomas Bürkli
Does this help?
Hi @Jeremy West,
if I understood correctly, you'd like to manage all tasks for your subcontractor in another project, right?
I could see two other possible ways (besides the security levels @Tom Lister mentioned):