Skip to content

None of the custom close reason fields are validated #1732

@Oaphi

Description

@Oaphi

We do not have any validation for custom close reasons, which makes it possible to create empty reasons:

Image

The resulting reason looks quite bizarre in the list:

Image

More importantly, since we have no validations, another bug has gone unnoticed - that we silently swallow close reason creation errors

Metadata

Metadata

Assignees

Labels

complexity: easyIssues that should take limited effort to resolve/fix/build.priority: low

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions