We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug in current situation
Entity Dashboard - Request for AGM Extension- AGM must be held by Date mismatch between current and New dashboard
Link bug to the User Story
Impact of this bug Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low) High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce Steps to reproduce the behavior:
AGM must be held by Date mismatch between current and New dashboard
Actual/ observed behavior/ results
Expected behavior
The text was updated successfully, but these errors were encountered:
Pulling into sprint (and removing a P2). Note, this will need to be sized in our stand up.
Sorry, something went wrong.
Looks great @patrickpeinanw - moving to QA
Retested. Looks good
mstanton1
gunanagar
patrickpeinanw
No branches or pull requests
Describe the bug in current situation
Entity Dashboard - Request for AGM Extension- AGM must be held by Date mismatch between current and New dashboard
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:
https://test.business.bcregistry.gov.bc.ca/BC1082215
https://business-dashboard-test.web.app/BC1082215
AGM must be held by Date mismatch between current and New dashboard
Actual/ observed behavior/ results
Expected behavior
The text was updated successfully, but these errors were encountered: