CRM: Resolves 2874 - handle missing transaction status#30644
Conversation
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Crm plugin:
|
2b320eb to
c1617d2
Compare
|
Is this PR ready to review? I don't see any file to check. |
|
For some reason 321a802 showed as empty. Repushed that commit. |
cleacos
left a comment
There was a problem hiding this comment.
It works as expected.
LGTM!
|
A PHP notice was making tests fail. @cleacos care to check again? ;^) |
a52e010 to
2322878
Compare
Resolves Automattic/zero-bs-crm#2874 - handle missing transaction status
Proposed changes:
If a transaction was synced with an unofficial status, the transaction status dropdown when editing will show as if the initial status is selected (generally "Succeeded").
This PR adds the unofficial status to the dropdown so that it accurately reflects the current transaction status.
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
In
trunkthe status will appear to be "Succeeded".In
fix/crm/2874-handle_missing_transaction_statusthe status will be the unofficial status you used.