Add labeling to epic tree creation/adding flow of confidential epics

Problem to solve

When adding work items to the tree view of a confidential epic- only confidential issues and epics are displayed in the list. Similarly, when a user creates an epic or issue within the tree view of a confidential epic- the epic or issue will be created as confidential.

Intended users

• Parker (Product Manager)
• Delaney (Development Team Lead)
• Sidney (Systems Administrator)
• Sam (Security Analyst)

User experience goal

Make it clear to users that only confidential items are allowed to be added or created within the tree of a confidential epic.

Proposal

For MVC:

• Add a title/header to each add/creation widget within the tree that explicitly calls out that the item being created/added will be confidential
• Add an info icon that trigger a tooltip of information. That seems like a small thing that can be iterated on. The tooltip could read something like, The parent epic is confidential and can only contain confidential epics and issues.
• Provide better labeling to input fields like Title and Find issue(s)

Titles/headers

• Add new epic: Create a confidential epic
• Add existing epic: Add an existing confidential epic
• Add new issue: Create a confidential issue
• Add existing issue: Add an existing confidential issue

Figma link

https://www.figma.com/file/wzapax982rLl4G2d83wS5b/219493-Only-suggest-confidential-issues-when-adding-issue-to-confidential-epic?node-id=50%3A227

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Users aren't anxious as to why they can't find epics and issues in their list, and understand that all items in a confidential tree must also be confidential.