UI Bug - Zone not populated in Zone specific API Token

Just an odd dashboard UI bug report

Repro:

  • Create a new API token with the Zone:Edit template
  • Save
  • Click edit on the API token

Expected:
Zone is set

Actual:
Zone is not set

Saving the zone leaves the zone set correctly, but it’s confusing why this is and it leaves doubts as to how the token will act if multiple zones are added and one needs to be removed from a token.

I just tried to recreate this by creating a new token using the template for Edit DNS, added one zone, saved, reviewed and zone is set.

I then edited the token, added another zone, it’s set as well.

I think I’m confused as to what’s confusing about this?

I think I’m confused as to what’s confusing about this?

It’s confusing when you can’t edit the things which you can see:

Main list:

Browser: Firefox / macOS
Plugins: all filtering plugins disabled