/releases/xxxxxxx/v2 should be able to create a new release

[jcristau]

I'm not sure if I'm doing something wrong here, but when trying to create a release I go to e.g. https://balrog.services.mozilla.com/releases/Widevine-4.10.2710.0/v2, then paste or upload the blob, but the form won't let me enter the product name, which means form submission fails. Going into devtools to replay the request having added the product to the request body does work.

[ademolaomosanya]

i'm an outreachy applicant
and i would like to work on this issue kindly asign me

[Raven49]

Kindly assign this task to me

[bhearsum]

@jcristau - can you still reproduce this? I wasn't able to with the latest main.

Is it possible you were on an Update page instead of a Create page? If so, not being able to edit the name is expected.

[jcristau]

It's possible I was on an Update page, I don't know the difference :)

[bhearsum]

It's possible I was on an Update page, I don't know the difference :)

The main indication is the page title. The route and UI are otherwise identical.

[jcristau]

Thanks, OK, so I guess the bug from my point of view is that /releases/doesnotexist/v2 should give me the "new release" page and pre-fill the name, instead of giving me an "update a release that does not exist and that you can't actually update" page. Does that sound reasonable?

[bhearsum]

Thanks, OK, so I guess the bug from my point of view is that /releases/doesnotexist/v2 should give me the "new release" page and pre-fill the name, instead of giving me an "update a release that does not exist and that you can't actually update" page. Does that sound reasonable?

Yeah, I think that makes sense. I guess the thing that surprises me is how you're getting to a page like that though? I guess it's a manually entered URL, as I don't see how you could get there via the UI.

[jcristau]

Correct. Partly because usually the new release I want to create is a variation on an existing one, but there's no "duplicate" button for releases like there is for rules. Partly because the "new release" button is on the /releases page which itself takes forever to load.

[bhearsum]

I've updated the summary to match what we've discussed. It looks like the fix here is going to involve a couple of things:

• Stop setting isNewRelease as part of the route/input to the Release edit/create page:

  balrog/ui/src/views/Releases/routes.js

  Line 27 in ca55f9a

  isNewRelease: true,

• Adjust

  balrog/ui/src/views/Releases/ReleaseV2/index.jsx

  Line 62 in ca55f9a

  isNewRelease,

  to stop taking this as an input, and determine for itself whether or not the release is new (presumably by querying the backend and seeing if it's a 404 or not).