Bugs

Export giving different amount of pending posts than exists

vor 6 MonatenAbgeschlossen

When I exported our requests, I found out there is a discrepancy between the web and the export. While we currently have 167 pending posts, there are 378 posts marked as pending in the export. I am attaching some examples. Why is that and how can it be fixed?

  • img/jn02sxqcf9tzlw2xbe0i5h2f
  • img/y46c7j07fimarl78yp2o4hvg
  • img/e0pckfnh37j453pgusaa5yc7
  • img/c6rcidm9n4y8j44th4gvowsk
und 2 weitere

3 Kommentare

  1. Shayan Taslim hat den Status auf Abgeschlossen gesetztvor 3 Monaten
  2. Shayan Taslimvor 6 Monaten

    I checked this and the difference comes from merged requests. The web UI counts only active, standalone requests. The CSV export currently includes all requests in the workspace, including requests that were merged into another request.

    When a request is merged, it is hidden from the main requests list, but it still exists in the database and keeps its original status. So some requests still show as Pending in the export even though they are no longer counted as pending in the web UI.

    In your workspace right now, there are 372 total pending requests in the export-style count, 168 active pending requests shown in the web UI, and 204 pending requests that have been merged into other requests.

    How would you prefer exports to behave: should the CSV match the web UI and exclude merged requests by default, or should it continue including merged requests but add a column like merged_into_request_id so they are easier to identify?

    1. Jana from DuoCardsvor 6 Monaten

      the CSV match the web UI and exclude merged requests please

  3. Shayan Taslim hat den Status auf In Bearbeitung gesetztvor 6 Monaten
  4. Shayan Taslimvor 6 Monaten

    Reviewing this now.