Skip to content

Disable firewall rule form submission when certain inputs (target, host filter, port filter) have been updated but not "added" #2068

@charliepark

Description

@charliepark

The situation: A user, new to the console, created a port filter as part of a firewall rule. They didn't Add that port filter as a part of their flow, and assumed that the port filter was created when they created the overall firewall rule. Being new to console, they didn't know what to look for on the list of firewall rules to see that the port filter was missing.

The idea with this issue, then, is to disable the overall form if certain inputs (target, host filter, port filter) have been modified but not "committed" (by clicking the "add target/filter" button).

I'm open to input / feedback on this, if people have opinions. Ultimately, the goal is to make sure that half-completed steps aren't misunderstood to be completed steps, so other solutions / ideas are welcome as well.

(Note that this is different from the earlier bug where hitting "enter" when in the port filter input submitted the overall form.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions