Skip to content

Conversation

@rousseldenis
Copy link

@rousseldenis rousseldenis commented Aug 22, 2024

In case of content transfer line by line, user wants to be recalled which origin location he comes from if he wants to transfer partially and put the remaining products back to source (e.g.: no more space on destination location)

@phschmidt @jbaudoux @sbejaoui @lmignon

An easy one 😅

@OCA-git-bot
Copy link
Contributor

Hi @guewen, @simahawk, @sebalix,
some modules you are maintaining are being modified, check this out!

@rousseldenis rousseldenis added enhancement New feature or request needs review labels Aug 22, 2024
@rousseldenis rousseldenis added this to the 16.0 milestone Aug 22, 2024
Copy link
Contributor

@jbaudoux jbaudoux left a comment

Choose a reason for hiding this comment

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

I'm not in favor of this change. The source location is marked as empty when you pick from there. If you partially process a quantity, you will still have to process the remaining quantity to the asked location. If you want to cancel remaining quantity and put back at source, there should be an explicit action with the right steps (and checks)

@rousseldenis
Copy link
Author

The source location is marked as empty when you pick from there.

What is your use case where source location is empty???

@jbaudoux
Copy link
Contributor

jbaudoux commented Oct 7, 2024

The source location is marked as empty when you pick from there.

What is your use case where source location is empty???

Someone takes from over-stock location N1 and starts unloading to stock location S2. Someone else moves from input location I3 to the empty N1.

@github-actions
Copy link

github-actions bot commented Feb 9, 2025

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 Feb 9, 2025
@github-actions github-actions bot closed this Mar 16, 2025
@rousseldenis
Copy link
Author

@jbaudoux This change has nothing to do with the flow itself.

It adds the source location in the message. Nothing more.

@rousseldenis rousseldenis reopened this Mar 20, 2025
@OCA-git-bot
Copy link
Contributor

Hi @sebalix, @simahawk, @guewen,
some modules you are maintaining are being modified, check this out!

Copy link
Contributor

@jbaudoux jbaudoux left a comment

Choose a reason for hiding this comment

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

I see the location source is displayed when last content is processed in location_content_transfer_complete
So it makes sense to display it here also :)

But can you do better than Content line ?

"message_type": "success",
"body": _("Content transfer to {} completed").format(location_dest.name),
"body": _(
"Content line transferred from %(location_name)s to %(location_dest_name)s",
Copy link
Contributor

Choose a reason for hiding this comment

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

What about

Suggested change
"Content line transferred from %(location_name)s to %(location_dest_name)s",
"Transferred from %(location_name)s to %(location_dest_name)s",

or

Suggested change
"Content line transferred from %(location_name)s to %(location_dest_name)s",
"Product %(product_name) transferred from %(location_name)s to %(location_dest_name)s",

and

Suggested change
"Content line transferred from %(location_name)s to %(location_dest_name)s",
"Package %(package_name) transferred from %(location_name)s to %(location_dest_name)s",

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 23, 2025
@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 Oct 19, 2025
@github-actions github-actions bot closed this Nov 23, 2025
@rousseldenis rousseldenis reopened this Jan 8, 2026
@OCA-git-bot
Copy link
Contributor

Hi @simahawk, @guewen, @sebalix,
some modules you are maintaining are being modified, check this out!

@rousseldenis
Copy link
Author

Merging this as very old. Improvement later.

/ocabot merge minor

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-925-by-rousseldenis-bump-minor, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Jan 8, 2026
Signed-off-by rousseldenis
@OCA-git-bot
Copy link
Contributor

@rousseldenis your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-925-by-rousseldenis-bump-minor.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

In case of content transfer line by line, user wants to be recalled which origin
location he comes from if he wants to transfer partially and put the remaining
products back to source (e.g.: no more space on destination location)
@rousseldenis rousseldenis force-pushed the 16.0-imp-shopfloor-location-content-message-dro branch from 3ec1027 to 9bfbe4b Compare January 8, 2026 12:47
@rousseldenis
Copy link
Author

/ocabot merge minor

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-925-by-rousseldenis-bump-minor, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 6fabed2 into OCA:16.0 Jan 8, 2026
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 60f4b5a. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved enhancement New feature or request merged 🎉 needs review 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.

4 participants