Update Confidentiality Sidebar and Badge to Support Test Cases
What does this MR do and why?
Relates to #422118 (closed)
As part of &11229 (closed), we will be adding support for creating and editing confidential test cases in the UI.
While test cases will be migrated to the work items framework mid-next year, this is an interim solution to help enable the Quality team to manage test cases within a single source of truth for ongoing confidential projects.
This MR:
- Updates various UI components used by the sidebar confidentiality widget to allow support for test cases.
- Adds a new
testCaseConfidentialQuery
andtestCaseConfidentialMutation
to be used by the widget. - Adds a new optional
workspaceType
prop toissuable_show_root
. This allowstest_case_show_root
to pass down the correct workspace type to theissuable_header
so that the correct confidentiality badge tooltip text can display. - Adds improvements to the copy text for the widget and the badge tooltip so that
test case
will now display instead oftest_case
Note: This widget has not been added to the test case sidebar yet. This will be added in #422120 (closed)
Screenshots or screen recordings
Test Case Header Confidentiality Badge
Now correctly references project members
rather than group members
and test_case
now shows as test case
Before | After |
---|---|
Test Case Sidebar (Future Changes)
The test case sidebar will have no changes in this MR and the widget will be added to the sidebar in #422120 (closed).
These screenshots show the future changes to help give an idea of what this will look like once the widget is applied.
Confidentiality OFF
Before | After |
---|---|
No widget |
Confidentiality ON
Before | After |
---|---|
No widget |
Other Confidentiality Badges and Sidebars
Other issuables that use confidentiality (issues, epics, incidents, etc.) should show no user-facing changes for the confidentiality badge and sidebar widget.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Ensure your local GDK has an Ultimate license applied
- Create a new group and project
- Visit the project, and go to Build > Test cases
- Create a new test case, and add the
/confidential
quick action to the description - Hover over the confidential badge in the test case header to verify the tooltip now shows
Only project members with at least the Reporter role can view or be notified about this test case.
- You can also test creating other issuables, such as issues, epics, tasks, incidents, etc., and verify the confidentiality badge tooltip as well as the confidential sidebar copy text remains unchanged and no regressions occur.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.