Fix adding confidential child tasks
What does this MR do and why?
Fix adding confidential child tasks
We removed querying the confidential attribute for work items. As a
result users were no longer able to add existing confidential tasks to
confidential issues.
The reason was that we check in the frontend if the existing child task
is confidential, when the parent is as well. As we no longer queried
confidential in our GraphQL query, we assumed that the task was not
confidential and showed an error. The user was not able to add the task
as we disabled the submit button.
Changelog: fixed
This was coming from the change in our query with !134883 (merged)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
| before_fix | after_fix |
How to set up and validate locally
- Create a confidential issue
- Create a task as part of the issue
- Unlink the task
- Try to add the task again
- Before: showed an error, with this MR: works again
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.