Voluntary Dissolution of Benefit Company - 1300911 BC LTD. (part 2)

[sienna-oldaccountdontuse]

ServiceNow incident:

INC0087423 Also relates to existing Zenhub ticket #7313

Contact information

Staff Name: Kat

Description

7313 was opened to voluntarily dissolve 1300911 BC LTD.

We completed part of it, but we have some missed requirements to finish:

• [x] Outputs - We need to make this available on paper only until we actually build the filing and outputs Directors are missing
• [x] Unaffiliate the account
• [x] when we update the party table, the directors need to remain active. We need to add them back in.
• [ ] COLIN ledger item - We need to find out why the filing didn't come back to COLIN.

NOTE for staff, no development required:

• User access - short-term fix is to unaffiliate them so they can't access the dashboard. When we build the filing

Ops Process

• [x] Add entity or relationships label to zenhub ticket ~- [ ] Add 'Priority1' label to zenhub ticket, if:~
  • If the business says it is a priority
  • BA can use their business knowledge and best judgement if it is a priority or not
  • How long the ticket has been open
  • If we are still unsure, reach out to other BAs in the guild
• [x] ~Assign zenhub ticket to the current developer on ops rotation~ Assigned to Thor so he can finish it
• [x] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
• [x] Reply All to IT Ops email (CC BA Inbox) and provide zenhub ticket number opened
• [ ] Dev/BAs to resolve issue
• [ ] DEV: Enter the time you worked on the ticket in the estimate
• [ ] DEV: Tell BA it is ready to review
• [ ] BAs review
• [ ] Add ticket to the current milestone of the code base the ops ticket was relating to (i.e., if it's a Name Request issue, assign to current entities milestone, etc.)
• [ ] Close Zenhub ticket
• [ ] Tell IT Ops to close the ServiceNow Incident

[sienna-oldaccountdontuse]

Hi again Kat,

I heard back from Linda, looks like we have a few more things to do to finish this off. Please let me know if this is blocking the client in any way. Would you like us to unaffiliate this entity from the client's account now, or after the work has been completed?

We are completing this work in a new ticket, #8580.

Thanks, Sienna

[sienna-oldaccountdontuse]

Thor worked on this, I verified:

• [ ] Outputs - We need to make this available on paper only until we actually build the filing and outputs Outputs are hidden, but didn't we make a more neutral message for disabled outputs? Because this filing was completed after March 10 2019.
• [x] Directors are there
• [x] Unaffiliate the account
• [ ] COLIN ledger item - We need to find out why the filing didn't come back to COLIN. Still missing, when should I see it, maybe tomorrow?

[thorwolpert]

Please close this

[janisrogers]

@Sienna-Blumstengel Are we still anticipating that the filing will show up in COLIN?

[janisrogers]

Comment in COLIN: THE VOLUNTARY DISSOLUTION WAS PROCESSED IN THE NEW BUSINES REGISTRY APPLICATION ON MAY 14, 2021. DUE TO SYSTEM LIMITATIONS IT REMAINED ACTIVE IN CORPORATE ONLINE AND HAD TO BE MANUALLY MADE HISTORICAL BY STAFF