Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orders and Fulfilments Report gives slug when producer and hub specified #4406

Closed
lin-d-hop opened this issue Oct 25, 2019 · 3 comments
Closed
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.

Comments

@lin-d-hop
Copy link
Contributor

Description

A user has reported that the Orders and Fulfilments report has changed in functionality. Thinking the report just wasn't working for them it disrupted their whole week, however we've now tracked down the issue.

Expected Behavior

A user who is a producer and a hub should be able to enter details into the producer and hub fields on the reports and get sensible data out. This is consistent with usage of OFN in other areas of the platform and allows for specific cases in which managers have multiple producers and hubs yet still want to be able to extract data for a single producer/hub.

This should work (currently slug):
OFN not working

As should this (currently slug):
OFN not working2

Actual Behaviour

when a user who is a hub and a producer inputs into BOTH the hub AND producer fields in the report they get a Slug 500 Error.

This does work:
OFN working

Steps to Reproduce

  1. Go to Orders and Fulfilments report
  2. Enter a produce/hub in both the Producer and Hub field
  3. Wait for timeout then see slug

Workaround

If you only include the Producer/Hub in one field you don't get the error. This workaround is acceptable however inconsistent with usage of OFN in other parts of the platform.
Not receiving an error message makes this confusing and troubling to the user.

Severity

bug-s3: a feature is broken but there is a workaround

Your Environment

  • Version used: UK - Bamboo
  • Browser name and version:
  • Operating System and version (desktop or mobile):

Possible Fix

@lin-d-hop lin-d-hop added the bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround. label Oct 25, 2019
@lin-d-hop
Copy link
Contributor Author

Reports are a mess. This might be 20mins or might be 20 days. Not a papercut

@kirstenalarsen
Copy link
Contributor

@lin-d-hop you think also too risky / confusing to set new developers on it? I suspect so . .

@lin-d-hop
Copy link
Contributor Author

Closing. Can reopen if still an issue on new reports code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.
Projects
None yet
Development

No branches or pull requests

2 participants