8000 fix: set default user value only if enabled by vorasmit · Pull Request #20715 · frappe/frappe · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: set default user value only if enabled #20715

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

Merged
merged 1 commit into from
May 22, 2023

Conversation

vorasmit
Copy link
Contributor

Following is the screenshot of the setting in user permission:

image

Existing Behaviour:

  • If there is only one user permission (say for warehouse), its always set as default in all doctypes.
  • If there are more than one permission for the warehouse, it will identify default as per settings.

Issue:
When there is more than one Warehouse field in a doctype, it sets the default for all the fields. Most of the time, it's not supposed to be the same. eg: from_warehouse has to be different from to_warehouse.

@vorasmit vorasmit requested review from a team and shariquerik and removed request for a team April 15, 2023 14:14
@stale
Copy link
stale bot commented Apr 22, 2023

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing.

@stale stale bot added the inactive label Apr 22, 2023
@vorasmit
Copy link
Contributor Author

keep alive

@stale stale bot removed the inactive label Apr 24, 2023
@phot0n phot0n requested review from surajshetty3416 and removed request for shariquerik April 28, 2023 10:16
@stale
Copy link
stale bot commented May 5, 2023

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing.

@stale stale bot added the inactive label May 5, 2023
@vorasmit
Copy link
Contributor Author
vorasmit commented May 6, 2023

keep alive

@stale stale bot removed the inactive label May 6, 2023
@phot0n
Copy link
Contributor
phot0n commented May 9, 2023

@surajshetty3416 can you take a look at this?

Copy link
Member
@surajshetty3416 surajshetty3416 left a comment

Choose a reason for hiding this comment

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

@vorasmit Can you share the behaviour after fix? How does it resolve the issue?

It looks like it'll still set same value if "is_default" is checked.

@surajshetty3416 surajshetty3416 self-assigned this May 16, 2023
@vorasmit
Copy link
Contributor Author
vorasmit commented May 16, 2023

Before

is_default-user_perm-before

After

is_default-user_perm

It will set the default value only if checked. Else it wouldn't set the default value.

@vorasmit vorasmit requested a review from surajshetty3416 May 16, 2023 10:26
@deepeshgarg007 deepeshgarg007 merged commit 0c5948b into frappe:develop May 22, 2023
@vorasmit vorasmit deleted the default-user-perm branch May 22, 2023 07:59
@deepeshgarg007 deepeshgarg007 added the defer backport Backports for some PR are deferred for a week or two to test them properly before releasing label May 22, 2023
83BC @github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2023
@ankush ankush added backport version-14-hotfix backport to version 14 and removed defer backport Backports for some PR are deferred for a week or two to test them properly before releasing labels Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport version-14-hotfix backport to version 14
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0