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

Prevent non-regulated operations from being assigned a BORO ID #2453

Closed
3 of 6 tasks
BCerki opened this issue Nov 7, 2024 · 0 comments
Closed
3 of 6 tasks

Prevent non-regulated operations from being assigned a BORO ID #2453

BCerki opened this issue Nov 7, 2024 · 0 comments
Assignees
Labels

Comments

@BCerki
Copy link
Contributor

BCerki commented Nov 7, 2024

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

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants