Keeping an item internal
Every item carries a privacy level, internal or external, and internal means invisible to anyone on a client role.
- Open the item and look at Task Privacy in the details panel. Trackers also show the level as a small badge next to the title in the list.
- To change it, click Actions, then Change Status, then pick Internal or External under Select Privacy Type, and confirm with Change Status.
- When you create something, choose the level in the create dialog. The Add Request dialog asks for Privacy on its first step. The task and subtask dialogs ask on their second step and default to Internal.
- Check the level before you write anything you would not say on the client call. It takes a second, and the setting sits on the item itself.
Hidden means hidden everywhere it matters, not just in the list. Internal items are left out of the records a client can load, out of the counts and stat tiles they see, and out of the notification fan-out, so nobody is pinged about a record they cannot open. It is enforced on the server, so there is no address to guess.
Privacy carries through triage. If an unsorted request was internal, the issue or feature request it becomes is internal too, and you do not have to remember to reapply it at the moment you are least likely to be thinking about it.
Older records created before privacy was required can come back with nothing set. Those read as Internal, which is the safe direction to fail in.
See this on your own workflow
This is the product as it stands today. A call is where you find out which parts of it your team would turn on, and what a deployment looks like.
partnerships@dhcertainty.com