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.

Sign up for GitHub

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

Jump to bottom

The Expected close date should be correct when the user is selecting the current date for the expected closed date. #647

Closed
Sanjaybhattwebkul opened this issue Nov 9, 2021 · 3 comments
Closed

The Expected close date should be correct when the user is selecting the current date for the expected closed date. #647

Sanjaybhattwebkul opened this issue Nov 9, 2021 · 3 comments
Assignees
@jitendra-webkul
Labels
Bug Fixed Bug

Comments

@Sanjaybhattwebkul
Copy link
Contributor

CRM Version: V1.2.0

Steps To reproduce--

1. Log in as Admin/User.
2. Create a new lead and select the current date for the expected close date.
3. Try to view lead and expected close date.

Actual result: The Expected close date is not correct when the user is selecting the current date for the expected closed date. Please find the below screenshot.

Expected result: The Expected close date should be correct when the user is selecting the current date for the expected closed date.

Close-date
jitendra-webkul added a commit to jitendra-webkul/bagisto-crm that referenced this issue Nov 9, 2021
@jitendra-webkul
Issue krayin#647 fixed
da86b91
@jitendra-webkul jitendra-webkul mentioned this issue Nov 9, 2021
Merged
jitendra-webkul added a commit that referenced this issue Nov 9, 2021
@jitendra-webkul
Merge pull request #649 from jitendra-webkul/master
ff1c3fc 
Issue #647 fixed
@Sanjaybhattwebkul
Copy link
Contributor Author

Sanjaybhattwebkul commented Nov 9, 2021 •
edited
Loading

@jitendra-webkul
If the expected close date is the current date, then the date should look like 9 Nov 2021

jitendra-webkul added a commit to jitendra-webkul/bagisto-crm that referenced this issue Nov 9, 2021
@jitendra-webkul
Issue krayin#647 fixed
44777df
@jitendra-webkul jitendra-webkul mentioned this issue Nov 9, 2021
Merged
jitendra-webkul added a commit that referenced this issue Nov 9, 2021
@jitendra-webkul
Merge pull request #651 from jitendra-webkul/master
1be2379 
Issue #647 fixed
@jitendra-webkul
Copy link
Member

Fixed, check again

@Sanjaybhattwebkul
Copy link
Contributor Author

@jitendra-webkul
Thanks, now this issue is fixed. so I am closing this issue.
And I have attached a screenshot for future reference.

fixed-l

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

@jitendra-webkul jitendra-webkul

Labels
Bug Fixed Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jitendra-webkul @Sanjaybhattwebkul