QA » openQA Project » openQA Tests

The referenced jira issue is a "Dev" subtask for SLED and it's tracked by the "Desktop" team. https://jira.suse.de/issues/?jql=%22External%20Id%22%20~%20%22316134%22 shows all related tickets. This new jira based workflow is a mess :,(

We can plan for ourselves how to test it manually once or think about automation but for now I would not care about an "offical feature test"

Nice catch, we definitely should not do same thing twice, so I lower priority.
SR for SLE15: https://build.suse.de/request/show/184338

Both SRs for SLE and TW are accepted 4 days ago, i.e. current/next builds should how the feature in action. If you like give it a quick manual test and inform the Desktop team about the test results, e.g. with a comment in the various duplicate jira tickets. Or we just wait for the Desktop team to do it. In that case again we have choices, e.g. reject this ticket and see what happens or set it to "Blocked" by the QA task in the jira ticket on the Desktop team. I leave the choice to you :)

As per last comment.

Let's give the Desktop team their time to validate that feature. We can catch in M25 if they don't

I will track the QA Task on the desktop team.

Grace has set the QA task to done.

The comment lists the detailed test results. I guess this should be enough for now.