-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
[HOLD for payment 2025-02-04] [$250] Report fields - Feature can be enabled in collect workspace #50472
Comments
Triggered auto assignment to @slafortune ( |
We think that this bug might be related to #wave-control |
@slafortune FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
Edited by proposal-police: This proposal was edited at 2024-10-09 21:40:29 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
App/src/libs/actions/connections/index.ts Line 22 in 3a6676e
What changes do you think we should make in order to solve the problem?
|
Job added to Upwork: https://www.upwork.com/jobs/~021844128989949063152 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allgandalf ( |
@slafortune , a thought:
|
@slafortune, @allgandalf Eep! 4 days overdue now. Issues have feelings too... |
bump on ^ @slafortune |
Report fields are a control feature, moving this to #expense. |
Perfect since everything Collect or Control is going to the Expenses Project Sorry for my delay @allgandalf
Report fields unrelated to any accounting integrations are not supported on the Collect workspace if connected to an accounting integration that is allowed on the collect workspace - report fields are enabled. When disconnecting - report fields should be removed. |
Sorry - some keyboard shortcut closed that 😱 |
Backend fix is on staging! I think you can hopefully move forward with testing the FE PR. |
Thanks a lot !, @mkzie2 please open the PR for review, also merge main |
lets prioritize this one @mkzie2 |
On my list today. |
@dangrous, @slafortune, @allgandalf, @mkzie2 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@mkzie2 when will you be able to get to this? |
@slafortune The PR was opened a long time ago #51717 and is under review now. |
Anything y'all need to get that PR pushed along? Let me know! Would love to get this merged this week. |
Hopeful to get this one merged in a day or two.... |
This issue has not been updated in over 15 days. @dangrous, @slafortune, @allgandalf, @mkzie2 eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
PR was merged. |
looks like this is on staging now! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-8 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 2025-02-04. 🎊 For reference, here are some details about the assignees on this issue:
|
@allgandalf @slafortune @allgandalf The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v9.0.46-1
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:
Precondition: user has Collect workspace.
Expected Result:
Report fields, as feature, available in Control workspace, disappeared from LHN.
Actual Result:
Report fields stays in LHN. User can access tab and add report filed to a collect workspace.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6628080_1728376180366.report_fields.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @slafortuneThe text was updated successfully, but these errors were encountered: