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
BUSINESS-EDIT-UI - Special Resolution - When COOPs where rules are paper only, starting a SR automatically puts rules in changed state and expects the SR section to be filled out
#18735
Closed
danaannab opened this issue
Nov 23, 2023
· 3 comments
The COOP CP1002526 was created by Ody. It had paper only filings and when an SR is started by Ashna, the app automatically changed the status in the View and Change Business Information screen to CHANGED in the RULES section of the screen.
Desired behaviour:
allow the SR to proceed
Show the Rules section as 'available on paper only'
Do not show the rules section as 'changed'
Verify if this issue also exists for paper-only memoranda
danaannab
changed the title
COOP - BUG: When COOPs where rules are paper only, starting a SR automatically put rules in changed state and expects the SR section to be filled out
COOP - BUG: When COOPs where rules are paper only, starting a SR automatically puts rules in changed state and expects the SR section to be filled out
Nov 23, 2023
seeker25
changed the title
COOP - BUG: When COOPs where rules are paper only, starting a SR automatically puts rules in changed state and expects the SR section to be filled out
BUSINESS-EDIT-UI - Special Resolution - When COOPs where rules are paper only, starting a SR automatically puts rules in changed state and expects the SR section to be filled out
Nov 29, 2023
The Coop we used was CP1002526. Please see screen capture below:
Private Zenhub Image
Private Zenhub Image
The COOP CP1002526 was created by Ody. It had paper only filings and when an SR is started by Ashna, the app automatically changed the status in the View and Change Business Information screen to CHANGED in the RULES section of the screen.
Desired behaviour:
Private Zenhub Image
The text was updated successfully, but these errors were encountered: