Uploader API not respecting name, description, start time, and attributes

[twalshOG]

Issue

Imported seems to be ignoring most of the launchImportRq values, including name, description, start time, and attributes

What is expected

The launch values would reflect the name, description, start time, and attributes I provided
*Ignoring start time makes some kind of sense and the JUnit file already includes this value

What am I seeing

Uploader seems to ignore everything but the JUnit file

What have I tried

Tried with the native JUnit uploader from that comes with the basic docker setup, release 1.0.2, release 1.0.1 and a local build of the latest from the development branch.
Same result for regardless of which version of the uploader used.

Steps to reproduce

1. Run a test suite containing 1 passing test and 1 skipped test, that outputs a JUnit file
2. As a the super user go to the api page (localhost example: http://localhost:8080/ui/#api)
3. Open the /v1/plugin/{projectName}/{pluginName}/import post endpoint
4. Click the "Try it out' button
5. Add the params, choose the file created in step 1, and add launchImportRq as outlined here
   1. Make sure you include "skippedIsNotIssue"
   2. Add any other key value pair, suggest {"key": "env","value": "localhost"}
6. Click the "Execute" button and note that you get a 200 back.
   
7. Go to the "Launches" tab and note that you don't have any attributes and you have 1 test to investigate
   

Partial work around

Use the API to update the launch
*This does not address the skippedIsNotIssue not working issue

Example update body

{
  "mode": "DEFAULT",
  "description": "Perfect test suite",
  "attributes": [
    {
      "key": "env",
      "value": "localhost"
    }
  ]
}

Example JUnit result content

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="jest tests" tests="2" failures="0" errors="0" time="0.324">
  <testsuite name="some category for cataloguing tests" errors="0" failures="0" skipped="1" timestamp="2025-04-01T13:16:30" time="0.298" tests="2">
    <testcase classname="some category for cataloguing tests does something specific correctly" name="some category for cataloguing tests does something specific correctly" time="0.001">
    </testcase>
    <testcase classname="some category for cataloguing tests is a skipped test" name="some category for cataloguing tests is a skipped test" time="0">
      <skipped/>
    </testcase>
  </testsuite>
</testsuites>

[twalshOG]

@grabsefx assume this will likely fall on your plate sooner or later

[twalshOG]

@Pink-Bumblebee
Mind providing your insight?

[Pink-Bumblebee]

@twalshOG, could you clarify what kind of insights you are expecting?
The Business Analyst has been informed, and the developer has been notified as well. There’s nothing more to add at the moment.

[twalshOG]

@Pink-Bumblebee
The main insight I was looking for is if the team actually considers this is a bug and/or if there is a recommended workaround.