Skip to content
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

🐛 [BUG] - 現金流量表前期餘額沒有正確計算 #2737

Closed
1 task done
TinyMurky opened this issue Oct 9, 2024 · 2 comments · Fixed by #2739
Closed
1 task done

🐛 [BUG] - 現金流量表前期餘額沒有正確計算 #2737

TinyMurky opened this issue Oct 9, 2024 · 2 comments · Fixed by #2739
Assignees
Labels
5 hard level 5 bug Something isn't working

Comments

@TinyMurky
Copy link
Contributor

Searched for similar issues

  • YES, I have searched for similar issues.

Time of occurrence

2024/10/9

Device

None

Other Device

No response

Device Version

No response

OS

Linux

OS Version

No response

Browsers

No response

Other Browser

No response

Browser Version

No response

Reproduction URL

http://localhost:3000/users/reports/financials/view/10000001

Reproduction steps

- 新增一筆含有現金的分錄(時間選早一點)
- 然後建立cash flow的時候不要把建立的分錄包含進去

Current Result

- 會發現Cash flow會沒有出現期初現金

Screenshots

建立的傳票
2024-10-09_11-06

產生兩張 cash flow( 1-110-9 和 10-910/10)
2024-10-09_11-08

正確的( 1-1~10-9)
2024-10-09_11-10

錯誤的(10-9~10/10)
2024-10-09_11-12

Logs

No response

Expected Result

需要先把前期現金算出來
@TinyMurky TinyMurky added bug Something isn't working 5 hard level 5 labels Oct 9, 2024
@TinyMurky TinyMurky self-assigned this Oct 9, 2024
@TinyMurky TinyMurky added this to the v0.9.0 Beta Release milestone Oct 9, 2024
@TinyMurky
Copy link
Contributor Author

TinyMurky commented Oct 9, 2024

修復 (10-1~10-9)
image

@TinyMurky TinyMurky linked a pull request Oct 9, 2024 that will close this issue
11 tasks
@TinyMurky
Copy link
Contributor Author

took 1 hours
done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 hard level 5 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant