Skip to content

Whenever we have a final state that you shouldn't be able to change, you should be prevented from changing it -- at the model level -- validation error (API or UI) #5569

@ruestitch

Description

@ruestitch

Summary

Whenever you have a state you shouldn't be able to change, you should be prevented from changing it.

Why?

making things consistent

Details

There are two remaining models where we have endpoints you shouldn't retreat from.

Account Request -- rejected or cancelled
Audit -- finalized

Enforce that you can't change these on the models

Criteria for completion

  • behaviour as described
  • tests to support behaviour as descrived
  • no user guide change needed

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions