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

[12.0][FIX] partner_statement: Covers the case where name and ref are strictly the same in account_move_line #601

Closed
wants to merge 1 commit into from

Conversation

cvinh
Copy link
Contributor

@cvinh cvinh commented Jul 31, 2019

Fixes the following use case :
If the fields name and ref are the same in account_move_line, nothing appears in the description column of the reports

@cvinh cvinh changed the title [FIX] Covers the case where name and ref are strictly the same in account_move_line [12.0-partner_statement] Covers the case where name and ref are strictly the same in account_move_line Jul 31, 2019
@cvinh cvinh changed the title [12.0-partner_statement] Covers the case where name and ref are strictly the same in account_move_line [12.0][FIX] partner_statement: Covers the case where name and ref are strictly the same in account_move_line Jul 31, 2019
@cvinh cvinh force-pushed the 12.0-fix_partner_statement_name_ref branch from 0e48750 to 4ffef05 Compare July 31, 2019 11:01
@gdgellatly
Copy link
Contributor

This looks wrong to me. It appears to break the case where they aren't the same, however one is in the other, and you would have both appear.

@MiquelRForgeFlow
Copy link
Contributor

and rebase

@MiquelRForgeFlow
Copy link
Contributor

Superseded by #652.

Copy link
Contributor

@MiquelRForgeFlow MiquelRForgeFlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be closed.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 27, 2022
@github-actions github-actions bot closed this Jan 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants