Skip to content
Snippets Groups Projects
Closed Testing data in the development database is not valid
  • View options
  • Testing data in the development database is not valid

    • View options
  • Closed created

    Summary

    When starting a fresh instance of queue in development mode, the database is filled with some data. There are 3 labs, one for COPL and two for A&D. The requests for the second A&D lab seem to be attributed to COPL, making it impossible for TAs to actually resolve the requests. The second button for getting the next request from the other lab is missing. Any new requests created via the interface itself do work properly. If a new request is made for the second lab, TAs get a second button to handle the request from the other lab as intended.

    In addition, the labs have no names (name is either empty or null), while this is a mandatory field when creating or editing labs.

    The requests page shows requests for COPL and A&D: Screenshot_20191007_174950

    Clicking on a request to get more details shows that the request is for A&D instead: Screenshot_20191007_174802

    There are no requests for the lab of COPL: Screenshot_20191007_174831

    Steps to reproduce

    1. Start a fresh instance of queue
    2. Log in as assistant2
    3. Go to requests
    4. Observe that requests of the second lab cannot be taken, even though they are displayed.
    5. Observe that requests for COPL in the overview show as requests for A&D on the detail page of each request.

    Possible Fix

    The initial data needs to be fixed.

    Attributes

    Assignees

    None

    Labels

    Milestone

    None

    Dates

    Start: None

    Due: None

    Time tracking

    No estimate or time spent

    Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first