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
BORO IDs are only assigned to Regulated Operations - so this includes OBPS Regulated Operations, New Entrants and Opt-ins. Those who do NOT get a BORO ID include all the non-regulated operations - so this includes Reporting Operations, Potential Reporting Operations and EIOs.
Currently in the app, all operations except EIOs can be assigned a BORO ID.
Acceptance Criteria
raise an error in the boro_id endpoint if anyone tries to assign an ID to one of the registration purposes that isn't allowed (add to the raise error line for EIOs)
in the BoroIdWidget, conditionally hide the "Issue BORO ID" button for operations that aren't allowed it (again, update the bit hiding it for EIOs)
add tests for ^
Definition of Done
first
second
third
Additional context
Add any other context about the task here.
Or here
The text was updated successfully, but these errors were encountered:
Describe the task
BORO IDs are only assigned to Regulated Operations - so this includes OBPS Regulated Operations, New Entrants and Opt-ins. Those who do NOT get a BORO ID include all the non-regulated operations - so this includes Reporting Operations, Potential Reporting Operations and EIOs.
Currently in the app, all operations except EIOs can be assigned a BORO ID.
Acceptance Criteria
Definition of Done
Additional context
The text was updated successfully, but these errors were encountered: