Skip to content

"started" requests that should be "fulfilled" #5326

@cielf

Description

@cielf

Summary

Fix problem where it's possible to make an already fulfilled request "started"

Details

If you view an unstarted request from two different windows (whether or not on the same machine), click fulfil, and save the distribution on the first one, then click 'fulfill' on the second, the request is changed to "started" -- it doesn't check that it's already fulfilled.

In this case, we should give an error indicating that the request has already been fulfilled, and not change the status.

This should be handled at the model level -- if something is fulfilled, you should not be able to change it.

See

Also provide a migration to clean up any requests that have a scheduled or completed distribution associated with them and are "started".

Criteria for completion

  • behaviour as described
  • automated tests to confirm behaviour
  • migration to clean up requests with this issue (this already exists, but will need to be invoked again)
  • No user guide changes 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