Best way to give 3rd party access to only certain tickets?

Question

We currently work with a 3rd party provider and are looking to give them access to just tickets on the backlog that are relevant to them.

Using the following method I have managed to nearly achieve what I am looking for however I am unable to rank the tickets as independent tickets and instead they can only be ranked within the bounds of the parent ticket (Epic).

Current solution

* Main board is a nextgen board
* Have created a new project with a classic board based on a filter (project in (ENA, PSD) AND status NOT IN (Done, Abandoned) AND labels = 3rdParty ORDER BY Rank ASC
* Ranking is enabled on the classic board

All tickets with the label are being pulled through to the new board correctly, however I am unable to rank them outside of the parent ticket. When looking in the backlog on the classic board all tickets are showing as a sub-task of PSD-x (which is the EPIC)

Is there either a setting to change this behaviour or a better way to achieve the same outcome?

Many thanks

Rick Pickles · Answer

Thanks Oliver

I had started with a company-managed project, but due to some team requirements with workflow that was difficult to achieve in our heavily customised environment I needed to move to team-managed.

Frustratingly this is the only remaining requirement I am struggling with on the team-managed board :(

Rick

Oliver Siebenmarck {Polymetis Apps} · Answer

Hi @Rick Pickles ,

I would approach this a bit differently, even though I like that you use labels.

However, using Issue Security Levels should be better suited, as you could keep all tickets in the same project and have them all rank on the same board.

The way to do this would be to set up an Issue Security Scheme with two levels, for example internal and external. You can then give access to each security level using groups, project roles and so on. You can also pick a default security level, so you can choose whether to have the 3rd party see new tickets immediately or not.

The only downside here is that you'll need a company-managed project. Next-gen team-managed projects do not support Issue Security Levels.

Hope that helps,
 Oliver