You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
As should this (currently slug):
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:
Steps to Reproduce
Go to Orders and Fulfilments report
Enter a produce/hub in both the Producer and Hub field
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
The text was updated successfully, but these errors were encountered:
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
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):
As should this (currently slug):
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:
Steps to Reproduce
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
Possible Fix
The text was updated successfully, but these errors were encountered: