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
{{ message }}
Repository navigation
[HOLD for payment 2024-08-01] Sage Intacct- "Entity" menu is empty and can not be navigated in Sage Intacct #45514
Version Number: 9.0.7-4 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Action Performed:
The user has a workspace policy connected to Sage Intacct
Navigate to Workspace settings > Accounting
Go to the "Entity" menu
Expected Result:
The user can navigate to the "Entity" page and change the entity
Actual Result:
The "Entity" menu is empty and cannot be navigated
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Hi 👋 It seems that the backend returned empty entities in data and that's why you can't navigate to them. I have some entities in my account and I can normally navigate to the page.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Just to confirm, @NikkiWines, is this message correct? I'm relatively new here, and I couldn't find information about paying for PR review without reviewing the issue/proposal first. Thanks a lot.
No, in this case it's wrong, since you reviewed this PR you are eligible for compensations. The automation didn't catch it cause you weren't assigned to this issue. I'll add the appropriate labels so we can provide the appropriate comp
Activity
melvin-bot commentedon Jul 16, 2024
Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 16, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
puneetlath commentedon Jul 16, 2024
This is under beta, so demoting from being a deploy blocker.
war-in commentedon Jul 17, 2024
Hi 👋 It seems that the backend returned empty
entitiesindataand that's why you can't navigate to them. I have some entities in my account and I can normally navigate to the page.Screen.Recording.2024-07-17.at.13.32.38.mov
14 remaining items
melvin-bot commentedon Jul 25, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 25, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-08-01. 🎊
melvin-bot commentedon Aug 1, 2024
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
brunovjk commentedon Aug 2, 2024
Just to confirm, @NikkiWines, is this message correct? I'm relatively new here, and I couldn't find information about paying for PR review without reviewing the issue/proposal first. Thanks a lot.
NikkiWines commentedon Aug 2, 2024
No, in this case it's wrong, since you reviewed this PR you are eligible for compensations. The automation didn't catch it cause you weren't assigned to this issue. I'll add the appropriate labels so we can provide the appropriate comp
melvin-bot commentedon Aug 2, 2024
Triggered auto assignment to @abekkala (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.NikkiWines commentedon Aug 2, 2024
@abekkala can we provide comp to @brunovjk since they reviewed my PR to fix this issue 🙇 thanks!
brunovjk commentedon Aug 2, 2024
Good to know :D Thank you very much @NikkiWines
abekkala commentedon Aug 2, 2024
PAYMENT SUMMARY:
abekkala commentedon Aug 2, 2024
@brunovjk payment sent and contract ended- thank you! 🎉