[jira] [Assigned] (OFBIZ-7377) Introduce the option for specifying Check (Reference) Number upon using Check as payment method during ordering

2019-07-27 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-7377:
---

Assignee: Aishwary Shrivastava  (was: Amit Gadaley)

> Introduce the option for specifying Check (Reference) Number upon using Check 
> as payment method during ordering
> ---
>
> Key: OFBIZ-7377
> URL: https://issues.apache.org/jira/browse/OFBIZ-7377
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: OrdPmt.png
>
>
> Currently there is no option during ordering to specify the actual Check 
> Number that could be used for making payment upon selecting Check as payment 
> method.
> We could provide a text entry box for recording check number and same could 
> be set as Payment.PaymentRefNumber upon order creation. 
> Please refer to attached screenshot



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen

2019-04-27 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10992:
-
Flags: Patch

> No pre-filled value while selecting "facilityId To" on Transfer Inventory 
> Item screen
> -
>
> Key: OFBIZ-10992
> URL: https://issues.apache.org/jira/browse/OFBIZ-10992
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk
>Reporter: Aishwary Shrivastava
>Assignee: Swapnil M Mane
>Priority: Minor
> Attachments: NewFacility.png, OFBIZ-10992.patch, 
> TransferInventoryItem.png
>
>
> While creating Transfer Inventory Item from warehouse, there are no prefiled 
> values in selecting FacilityId To.
> Steps to regenerate:
>  # Go to Facilities.
>  # Select Inventory Xfers.
>  # Create Transfer Inventory Item From any Warehouse.
>  # Fill values in the feilds.
>  # Try to click on FacilityIdTo field
> Attached the screenshots for creating new inventory item transfer screen and 
> new facility screen.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen

2019-04-27 Thread Aishwary Shrivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827752#comment-16827752
 ] 

Aishwary Shrivastava commented on OFBIZ-10992:
--

Added patch for the fix, thanks [~pawan.verma] for the help.

Changed parameter from "facilityIdTo" to "facilityId" in the form 
"CreateInventoryTransfer".

> No pre-filled value while selecting "facilityId To" on Transfer Inventory 
> Item screen
> -
>
> Key: OFBIZ-10992
> URL: https://issues.apache.org/jira/browse/OFBIZ-10992
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk
>Reporter: Aishwary Shrivastava
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: NewFacility.png, OFBIZ-10992.patch, 
> TransferInventoryItem.png
>
>
> While creating Transfer Inventory Item from warehouse, there are no prefiled 
> values in selecting FacilityId To.
> Steps to regenerate:
>  # Go to Facilities.
>  # Select Inventory Xfers.
>  # Create Transfer Inventory Item From any Warehouse.
>  # Fill values in the feilds.
>  # Try to click on FacilityIdTo field
> Attached the screenshots for creating new inventory item transfer screen and 
> new facility screen.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen

2019-04-27 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10992:
-
Attachment: OFBIZ-10992.patch

> No pre-filled value while selecting "facilityId To" on Transfer Inventory 
> Item screen
> -
>
> Key: OFBIZ-10992
> URL: https://issues.apache.org/jira/browse/OFBIZ-10992
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk
>Reporter: Aishwary Shrivastava
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: NewFacility.png, OFBIZ-10992.patch, 
> TransferInventoryItem.png
>
>
> While creating Transfer Inventory Item from warehouse, there are no prefiled 
> values in selecting FacilityId To.
> Steps to regenerate:
>  # Go to Facilities.
>  # Select Inventory Xfers.
>  # Create Transfer Inventory Item From any Warehouse.
>  # Fill values in the feilds.
>  # Try to click on FacilityIdTo field
> Attached the screenshots for creating new inventory item transfer screen and 
> new facility screen.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen

2019-04-27 Thread Aishwary Shrivastava (JIRA)
Aishwary Shrivastava created OFBIZ-10992:


 Summary: No pre-filled value while selecting "facilityId To" on 
Transfer Inventory Item screen
 Key: OFBIZ-10992
 URL: https://issues.apache.org/jira/browse/OFBIZ-10992
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Trunk
Reporter: Aishwary Shrivastava
Assignee: Aishwary Shrivastava
 Attachments: NewFacility.png, TransferInventoryItem.png

While creating Transfer Inventory Item from warehouse, there are no prefiled 
values in selecting FacilityId To.

Steps to regenerate:
 # Go to Facilities.
 # Select Inventory Xfers.
 # Create Transfer Inventory Item From any Warehouse.
 # Fill values in the feilds.
 # Try to click on FacilityIdTo field

Attached the screenshots for creating new inventory item transfer screen and 
new facility screen.

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (OFBIZ-10963) Making Good Identifiers date controlled for making it reusable

2019-04-27 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava closed OFBIZ-10963.

Resolution: Fixed

> Making Good Identifiers date controlled for making it reusable
> --
>
> Key: OFBIZ-10963
> URL: https://issues.apache.org/jira/browse/OFBIZ-10963
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Reporter: Aishwary Shrivastava
>Assignee: Aishwary Shrivastava
>Priority: Minor
>
> Extend GoodIdentification entity and include fromDate and thruDate fields.
> It will enable the user to maintain multiple goodIdentifications of a product
> This may also make GoodIdentifiacation resuable.
> History can also be maintained for the product idenfifiers.
> For this, we need to check on all queries on Good Identification.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10963) Making Good Identifiers date controlled for making it reusable

2019-04-27 Thread Aishwary Shrivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827572#comment-16827572
 ] 

Aishwary Shrivastava commented on OFBIZ-10963:
--

Discarding this ticket as per the discussion in the developer mailing list.

We can resume it in future, if we find any good use cases for the 
implementation.

https://ofbiz.markmail.org/thread/dh35oljokc45gwqr

> Making Good Identifiers date controlled for making it reusable
> --
>
> Key: OFBIZ-10963
> URL: https://issues.apache.org/jira/browse/OFBIZ-10963
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Reporter: Aishwary Shrivastava
>Assignee: Aishwary Shrivastava
>Priority: Minor
>
> Extend GoodIdentification entity and include fromDate and thruDate fields.
> It will enable the user to maintain multiple goodIdentifications of a product
> This may also make GoodIdentifiacation resuable.
> History can also be maintained for the product idenfifiers.
> For this, we need to check on all queries on Good Identification.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10963) Making Good Identifiers date controlled for making it reusable

2019-04-27 Thread Aishwary Shrivastava (JIRA)
Aishwary Shrivastava created OFBIZ-10963:


 Summary: Making Good Identifiers date controlled for making it 
reusable
 Key: OFBIZ-10963
 URL: https://issues.apache.org/jira/browse/OFBIZ-10963
 Project: OFBiz
  Issue Type: Improvement
  Components: product
Reporter: Aishwary Shrivastava
Assignee: Aishwary Shrivastava


Extend GoodIdentification entity and include fromDate and thruDate fields.

It will enable the user to maintain multiple goodIdentifications of a product

This may also make GoodIdentifiacation resuable.

History can also be maintained for the product idenfifiers.

For this, we need to check on all queries on Good Identification.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-10749) Unable to submit set Billing form in order manager when payment method is EFT

2019-01-11 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-10749:


Assignee: Aishwary Shrivastava

> Unable to submit set Billing form in order manager when payment method is EFT
> -
>
> Key: OFBIZ-10749
> URL: https://issues.apache.org/jira/browse/OFBIZ-10749
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-SetCustomer.png, 10-ConsoleError.png, 2-Continue.png, 
> 3-AddProduct.png, 4-QuickFinalizeOrder.png, 5-EftAccount.png, 
> 6-TelecomNumber.png, 7-Address.png, 8-EFT.png, 9-BillingAddress.png
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main]
>  # Click on order entry
>  # Set customer and click on continue (Please refer attachment: 1-SetCustomer)
>  # Click continue on Enter Order Currency, Agreements, and Ship Dates page 
> (Please refer attachment: 2-Continue)
>  # Add product and click on Quick Finalize Order (Please refer attachment: 
> 3-AddProduct)
>  # On Quick Finalize Order page select UPS Air and click on EFT Account 
> (Please refer attachment: 4-QuickFinalizeOrder)
>  # Enter account details but do not select billing address and click on Save 
> button(Please refer attachment: 5-EftAccount)
>  # Add phone and email address and click on continue (Please refer 
> attachment: 6-TelecomNumber)
>  # Enter address (Please refer attachment: 7-Address)
>  # Click continue on Sales Order : Order Entry Order Terms page
>  # Select Electronic Fund Transfer on Sales Order : Order Entry Payment 
> Settings and click continue (Please refer attachment: 8-EFT)
>  # Enter billing address and click on continue (Please refer attachment: 
> 9-BillingAddress)
> Actual: Unable to Submit form and error message was displayed on console 
> (Please refer attachment: 10-ConsoleError)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-7469) No need to select mime type of content in E-commerce / Party Profile

2018-12-22 Thread Aishwary Shrivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727356#comment-16727356
 ] 

Aishwary Shrivastava commented on OFBIZ-7469:
-

Hello Deepak,

Another error is coming while verifying the issue, due to which I am unable to 
regerate this issue, created an JIRA ticket for the same, will get back to this 
as soon as I am done with this error.

Thanks!

https://issues.apache.org/jira/browse/OFBIZ-10746

> No need to select mime type of content in E-commerce / Party Profile
> 
>
> Key: OFBIZ-7469
> URL: https://issues.apache.org/jira/browse/OFBIZ-7469
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Deepak Nigam
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: MimeTypeSelection.png
>
>
> There is no need to provide drop-down from selecting mime type of the content 
> while uploading new file from ecommerce / view profile / file manager .
> As this is an old pattern, now we have 'tika' library to identity mime type 
> of a uploaded content.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10746) Error while uploading file in Ecommerce Profile's File Manager

2018-12-22 Thread Aishwary Shrivastava (JIRA)
Aishwary Shrivastava created OFBIZ-10746:


 Summary: Error while uploading file in Ecommerce Profile's File 
Manager 
 Key: OFBIZ-10746
 URL: https://issues.apache.org/jira/browse/OFBIZ-10746
 Project: OFBiz
  Issue Type: Bug
  Components: ecommerce
Affects Versions: Trunk
Reporter: Aishwary Shrivastava
Assignee: Aishwary Shrivastava
 Attachments: ErroUploadingFileOnFileManagerEcommerce.png

On uploading File in Ecommerce Profile's File Manager,

"The following required parameter is missing: [IN] 
[uploadPartyContentFile.partyContentTypeId]" error is displaying.

 

Steps to regenerate the issue:
 # Open Ecommerce on Ofbiz.
 # Login with any user.
 # Go to Profile.
 # Navigate down to File Manager.
 # Select Purpose.
 # Seletct Mime Type
 # Click upload.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-22 Thread Aishwary Shrivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727338#comment-16727338
 ] 

Aishwary Shrivastava commented on OFBIZ-10730:
--

Hello Arpit, 
Thanks for finding this issue, I have Fixed the distorted row of the Products 
and also improved the UI, to distinguish the products as per your suggestion. 

Please see the attached screenshot (5-UIAfterApplyingPatch) to view the 
improved UI.

 

Thanks

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png, 5-UIAfterApplyingPatch.png, 
> OFBIZ-10730.patch
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-22 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10730:
-
Attachment: 5-UIAfterApplyingPatch.png

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png, 5-UIAfterApplyingPatch.png, 
> OFBIZ-10730.patch
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-22 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10730:
-
Attachment: (was: OFBIZ-10730.patch)

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png, OFBIZ-10730.patch
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-22 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10730:
-
Attachment: OFBIZ-10730.patch

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png, OFBIZ-10730.patch
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-22 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10730:
-
Attachment: OFBIZ-10730.patch

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png, OFBIZ-10730.patch
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-21 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-10730:


Assignee: Aishwary Shrivastava

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-10730) UI improvements on splitship page of ecommerce

2018-12-21 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-10730:


Assignee: Aishwary Shrivastava

> UI improvements on splitship page of ecommerce
> --
>
> Key: OFBIZ-10730
> URL: https://issues.apache.org/jira/browse/OFBIZ-10730
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Aishwary Shrivastava
>Priority: Major
> Attachments: 1-Checkout.png, 2-SplitShipment.png, 
> 3-UI_Improvemennts.png, 4-Suggestion.png
>
>
> Steps to regenerate:
>  # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]
>  # Add multiple items to cart
>  # Click on Check Out on cart summary (Please refer attachment: 1-Checkout)
>  # Click on split shipment (Please refer attachment: 2-SplitShipment)
> Actual: UI is not proper on splitship page (Please refer attachment: 
> 3-UI_Improvemennts)
> Suggestion: IMO, adding a horizontal separator between products in assign 
> items section will be a good (Please refer attachment: 4-Suggestion)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-7469) No need to select mime type of content in E-commerce / Party Profile

2018-12-21 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-7469:
---

Assignee: Aishwary Shrivastava

> No need to select mime type of content in E-commerce / Party Profile
> 
>
> Key: OFBIZ-7469
> URL: https://issues.apache.org/jira/browse/OFBIZ-7469
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Deepak Nigam
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: MimeTypeSelection.png
>
>
> There is no need to provide drop-down from selecting mime type of the content 
> while uploading new file from ecommerce / view profile / file manager .
> As this is an old pattern, now we have 'tika' library to identity mime type 
> of a uploaded content.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-2584) Breadcrumbs should be shown on all the pages of eCommerce application

2018-11-24 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-2584:

Attachment: OFBIZ-2584.patch

> Breadcrumbs should be shown on all the pages of eCommerce application
> -
>
> Key: OFBIZ-2584
> URL: https://issues.apache.org/jira/browse/OFBIZ-2584
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Pranay Pandey
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: OFBIZ-2584.patch
>
>
> Right now in OOTB eCommerce application breadcrumbs are only shown for 
> catalog pages. It should be available on other pages too.
> e.g.
> If user goes on Contact Us page then: Home --> Contact Us should be shown in 
> breadcrumbs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-2584) Breadcrumbs should be shown on all the pages of eCommerce application

2018-11-24 Thread Aishwary Shrivastava (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697813#comment-16697813
 ] 

Aishwary Shrivastava commented on OFBIZ-2584:
-

The breadcrumbs on the catalog are managed by setting "TRAITS" in the sessions.
On pages like Contact us or Store policies, we can simply place the breadcrumb 
links on the FTL.
I have added breadcrumbs on the Anonymous contact us and logged in user's 
contact us. 
In the top navbar, I can also find more such pages like user profile, messages, 
quotes, requests, shopping list, order history, and Quick add, but these are 
restricted for the logged-in user only, so should I add the breadcrumbs here 
too?

 

Added patch for ContactUs and Anonymous ContactUs.

> Breadcrumbs should be shown on all the pages of eCommerce application
> -
>
> Key: OFBIZ-2584
> URL: https://issues.apache.org/jira/browse/OFBIZ-2584
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Pranay Pandey
>Assignee: Aishwary Shrivastava
>Priority: Minor
>
> Right now in OOTB eCommerce application breadcrumbs are only shown for 
> catalog pages. It should be available on other pages too.
> e.g.
> If user goes on Contact Us page then: Home --> Contact Us should be shown in 
> breadcrumbs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-2584) Breadcrumbs should be shown on all the pages of eCommerce application

2018-10-26 Thread Aishwary Shrivastava (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-2584:
---

Assignee: Aishwary Shrivastava

> Breadcrumbs should be shown on all the pages of eCommerce application
> -
>
> Key: OFBIZ-2584
> URL: https://issues.apache.org/jira/browse/OFBIZ-2584
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Pranay Pandey
>Assignee: Aishwary Shrivastava
>Priority: Minor
>
> Right now in OOTB eCommerce application breadcrumbs are only shown for 
> catalog pages. It should be available on other pages too.
> e.g.
> If user goes on Contact Us page then: Home --> Contact Us should be shown in 
> breadcrumbs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (OFBIZ-10239) Improve GeneralLedgerServices to set AcctgTrans's transition date as payment's effective date

2018-03-24 Thread Aishwary Shrivastava (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412498#comment-16412498
 ] 

Aishwary Shrivastava edited comment on OFBIZ-10239 at 3/24/18 10:00 AM:


Steps to verify:
 # Find an old unapplied payment, of type customer payment.
 # Recieve the Payment.
 # Go to the invoice.
 # scroll down to transactions.
 # Verify that transaction dates and posted dates are same.
 # Apply the patch.
 # Find another unapplied payment, of type customer payment.
 # repeat step 2, 3 and 4.
 # Verify that transaction date is now the effective date of the payment and 
posted date is the current date.

Thanks [~jacopoc] for providing the patch.


was (Author: aishwary):
Steps to verify:
 # Find an old unapplied payment, of type customer payment.
 # Recieve the Payment.
 # Go to the invoice.
 # scroll down to transactions.
 # Verify that transaction dates and posted dates are same.
 # Apply the patch.
 # Find another unapplied payment, of type customer payment.
 # repeat step 2, 3 and 4.
 # Verify that transaction date is now the effective date of the payment and 
posted date is the current date.

> Improve GeneralLedgerServices to set AcctgTrans's transition date as 
> payment's effective date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Whenever user applies a payment, the {color:#008000}transactionDate 
> {color}set on AcctgTransEntries is set by 
> {color:#80}now-timestamp{color}, this can result in wrong accounting 
> reports, if the payment was received earlier but applied later.
> For example, if someone receives a payment on 28 of Dec and applies the 
> payment on 3rd of Jan, the yearly accounting reports will show that 
> transaction in the new year, rather than in the previous year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10239) Improve GeneralLedgerServices to set AcctgTrans's transition date as payment's effective date

2018-03-24 Thread Aishwary Shrivastava (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412498#comment-16412498
 ] 

Aishwary Shrivastava commented on OFBIZ-10239:
--

Steps to verify:
 # Find an old unapplied payment, of type customer payment.
 # Recieve the Payment.
 # Go to the invoice.
 # scroll down to transactions.
 # Verify that transaction dates and posted dates are same.
 # Apply the patch.
 # Find another unapplied payment, of type customer payment.
 # repeat step 2, 3 and 4.
 # Verify that transaction date is now the effective date of the payment and 
posted date is the current date.

> Improve GeneralLedgerServices to set AcctgTrans's transition date as 
> payment's effective date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Whenever user applies a payment, the {color:#008000}transactionDate 
> {color}set on AcctgTransEntries is set by 
> {color:#80}now-timestamp{color}, this can result in wrong accounting 
> reports, if the payment was received earlier but applied later.
> For example, if someone receives a payment on 28 of Dec and applies the 
> payment on 3rd of Jan, the yearly accounting reports will show that 
> transaction in the new year, rather than in the previous year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10239) Improve GeneralLedgerServices to set AcctgTrans's transition date as payment's effective date

2018-03-24 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10239:
-
Description: 
Whenever user applies a payment, the {color:#008000}transactionDate {color}set 
on AcctgTransEntries is set by {color:#80}now-timestamp{color}, this can 
result in wrong accounting reports, if the payment was received earlier but 
applied later.

For example, if someone receives a payment on 28 of Dec and applies the payment 
on 3rd of Jan, the yearly accounting reports will show that transaction in the 
new year, rather than in the previous year.

  was:
Whenever user applies a payment, the {color:#008000}transactionDate {color}set 
on AcctgTransEntries is set by {color:#80}now-timestamp{color}, this can 
result in wrong accounting reports, if the payment was received earlier but 
applied latly. 

For example, if someone receives a payment on 28 of Dec and applies the payment 
on 3rd of Jan, the yearly accounting reports will show that transaction in the 
new year, rather than in the previous year.


> Improve GeneralLedgerServices to set AcctgTrans's transition date as 
> payment's effective date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Whenever user applies a payment, the {color:#008000}transactionDate 
> {color}set on AcctgTransEntries is set by 
> {color:#80}now-timestamp{color}, this can result in wrong accounting 
> reports, if the payment was received earlier but applied later.
> For example, if someone receives a payment on 28 of Dec and applies the 
> payment on 3rd of Jan, the yearly accounting reports will show that 
> transaction in the new year, rather than in the previous year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10239) Improve GeneralLedgerServices to set AcctgTrans's transition date as payment's effective date

2018-03-24 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10239:
-
Summary: Improve GeneralLedgerServices to set AcctgTrans's transition date 
as payment's effective date  (was: Improve GeneralLedgerServices to set 
transaction date as payment's effective date)

> Improve GeneralLedgerServices to set AcctgTrans's transition date as 
> payment's effective date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Whenever user applies a payment, the {color:#008000}transactionDate 
> {color}set on AcctgTransEntries is set by 
> {color:#80}now-timestamp{color}, this can result in wrong accounting 
> reports, if the payment was received earlier but applied latly. 
> For example, if someone receives a payment on 28 of Dec and applies the 
> payment on 3rd of Jan, the yearly accounting reports will show that 
> transaction in the new year, rather than in the previous year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10239) Improve GeneralLedgerServices to set transaction date as payment's effective date

2018-03-24 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10239:
-
Description: 
Whenever user applies a payment, the {color:#008000}transactionDate {color}set 
on AcctgTransEntries is set by {color:#80}now-timestamp{color}, this can 
result in wrong accounting reports, if the payment was received earlier but 
applied latly. 

For example, if someone receives a payment on 28 of Dec and applies the payment 
on 3rd of Jan, the yearly accounting reports will show that transaction in the 
new year, rather than in the previous year.

  was:Improved createAcctgTransAndEntriesForPaymentApplication and 
createAcctgTransAndEntriesForOutgoingPayment services to Set transaction date 
as payment's effective date.


> Improve GeneralLedgerServices to set transaction date as payment's effective 
> date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Whenever user applies a payment, the {color:#008000}transactionDate 
> {color}set on AcctgTransEntries is set by 
> {color:#80}now-timestamp{color}, this can result in wrong accounting 
> reports, if the payment was received earlier but applied latly. 
> For example, if someone receives a payment on 28 of Dec and applies the 
> payment on 3rd of Jan, the yearly accounting reports will show that 
> transaction in the new year, rather than in the previous year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10239) Improve GeneralLedgerServices to set transaction date as payment's effective date

2018-02-24 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-10239:
-
Attachment: OFBIZ-10239.patch

> Improve GeneralLedgerServices to set transaction date as payment's effective 
> date
> -
>
> Key: OFBIZ-10239
> URL: https://issues.apache.org/jira/browse/OFBIZ-10239
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Reporter: Aishwary Shrivastava
>Assignee: Aishwary Shrivastava
>Priority: Minor
> Attachments: OFBIZ-10239.patch
>
>
> Improved createAcctgTransAndEntriesForPaymentApplication and 
> createAcctgTransAndEntriesForOutgoingPayment services to Set transaction date 
> as payment's effective date.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-10239) Improve GeneralLedgerServices to set transaction date as payment's effective date

2018-02-24 Thread Aishwary Shrivastava (JIRA)
Aishwary Shrivastava created OFBIZ-10239:


 Summary: Improve GeneralLedgerServices to set transaction date as 
payment's effective date
 Key: OFBIZ-10239
 URL: https://issues.apache.org/jira/browse/OFBIZ-10239
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Aishwary Shrivastava
Assignee: Aishwary Shrivastava


Improved createAcctgTransAndEntriesForPaymentApplication and 
createAcctgTransAndEntriesForOutgoingPayment services to Set transaction date 
as payment's effective date.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-9911) Add ability to record Return Communication

2017-12-23 Thread Aishwary Shrivastava (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302381#comment-16302381
 ] 

Aishwary Shrivastava commented on OFBIZ-9911:
-

Thanks, Ratnesh Upadhyay, I have tested the patch with following steps:

1. Created Sales order: PASS
2. Shipped the item: PASS
3. Initiated the Return: PASS
4. Select the Item and accept the return: PASS
5. Verify the email received on the shipping email of Customer: PASS
6. Verify the Communication event on CommunicationEventReturn Entity: PASS
7. Verify the Communication on Party's Communication Screen: PASS


> Add ability to record Return Communication
> --
>
> Key: OFBIZ-9911
> URL: https://issues.apache.org/jira/browse/OFBIZ-9911
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order, party
>Reporter: Ratnesh Upadhyay
>Assignee: Rishi Solanki
> Attachments: OFBIZ-9911-CommunicationEventReturn-Entity.jpg, 
> OFBIZ-9911-FindCommByReturn-FilterRecords-Screen.jpg, 
> OFBIZ-9911-FindCommunicationByReturn-Screen.jpg, OFBIZ-9911.patch, 
> OFBIZ-9911.patch
>
>
> In OOTB we are having the ability to record order specific communication in 
> CommunicationEventOrder and the user can retrieve/review them from party > 
> communications screen but we don't have such support for return 
> communications. So It would be great to have an ability to record return 
> specific communication in the system.
> We have to implement following items to establish this feature :
> *Data Model Details:*
> - We will have to create new entity CommunicationEventReturn to record return 
> communication. It should have returnId and communicationEventId along with 
> other necessary fields.
> - We have to implement following view CommunicationEventAndReturn to fetch 
> return communications over screens as needed.
> *New Implementation Details:*
> - We have to add CRUD services for the new entity. 
> *Existing Implementation Details:*
> - We have to extend createCommunicationEvent service definition with retunId 
> field and extend the existing implementation to create the record in 
> CommunicationEventReturn based on supplied returnId parameter.
> - Also, we have to extend return related email services to provide returnId 
> in service context.
> *User Interface Details:*
> - In the current system we have Party > Communications > Find Communication 
> By Order screen, in the same way, we can add another screen to find 
> communication by return.
> - We can add return communication screenlet over Order Manager > Return > 
> Return History screen or we can add communication tab under Order > Return 
> screen, this is just a thought still thinking on it.
> - We can also provide communication tab in order component as well.
> Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for 
> discussion and inputs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (OFBIZ-9844) Replace Inline js with External js in renderTextField macro

2017-11-25 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-9844:
---

Assignee: Aishwary Shrivastava

> Replace Inline js with External js in renderTextField macro
> ---
>
> Key: OFBIZ-9844
> URL: https://issues.apache.org/jira/browse/OFBIZ-9844
> Project: OFBiz
>  Issue Type: Sub-task
>Reporter: Aditya Sharma
>Assignee: Aishwary Shrivastava
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (OFBIZ-9848) Replace Inline js with External js in renderDateTimeField macro

2017-11-25 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-9848:
---

Assignee: Aishwary Shrivastava

> Replace Inline js with External js in renderDateTimeField macro
> ---
>
> Key: OFBIZ-9848
> URL: https://issues.apache.org/jira/browse/OFBIZ-9848
> Project: OFBiz
>  Issue Type: Sub-task
>Reporter: Aditya Sharma
>Assignee: Aishwary Shrivastava
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OFBIZ-9770) CSS files defined through layoutSettings in GlobalActions are loaded twice

2017-10-28 Thread Aishwary Shrivastava (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223471#comment-16223471
 ] 

Aishwary Shrivastava commented on OFBIZ-9770:
-

Hi Aditya, I verified this patch and its working fine. 

> CSS files defined through layoutSettings in GlobalActions are loaded twice
> --
>
> Key: OFBIZ-9770
> URL: https://issues.apache.org/jira/browse/OFBIZ-9770
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
> Attachments: OFBIZ-9770.patch, screenshot-1.png
>
>
> CSS files added in GlobalActions screen of CommonScreens.xml are loaded twice.
> Css file jquery.jgrowl.min.css is loaded twice.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OFBIZ-8411) popup image takes full width of browser window for ecommerce multiflex theme

2017-10-28 Thread Aishwary Shrivastava (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223430#comment-16223430
 ] 

Aishwary Shrivastava commented on OFBIZ-8411:
-

I explored this issue and found that CSS for popup was not there in  style.css, 
which is style sheet of Multiflex.

I explored other theme's CSS and found that every other theme has CSS for popup 
class.
I think adding CSS for popup will do the work.

> popup image takes full width of browser window for ecommerce multiflex theme
> 
>
> Key: OFBIZ-8411
> URL: https://issues.apache.org/jira/browse/OFBIZ-8411
> Project: OFBiz
>  Issue Type: Bug
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Aishwary Shrivastava
> Attachments: OFBIZ-8411.patch
>
>
> go to https://localhost:8443/catalog/control/FindProductStore
> select multiflex theme
> go to ecommerce
> hover mouse over an image.
> notice that the width of popup image take width of browser window



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OFBIZ-8411) popup image takes full width of browser window for ecommerce multiflex theme

2017-10-28 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-8411:

Attachment: OFBIZ-8411.patch

Attaching Patch for this issue.

> popup image takes full width of browser window for ecommerce multiflex theme
> 
>
> Key: OFBIZ-8411
> URL: https://issues.apache.org/jira/browse/OFBIZ-8411
> Project: OFBiz
>  Issue Type: Bug
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Aishwary Shrivastava
> Attachments: OFBIZ-8411.patch
>
>
> go to https://localhost:8443/catalog/control/FindProductStore
> select multiflex theme
> go to ecommerce
> hover mouse over an image.
> notice that the width of popup image take width of browser window



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (OFBIZ-8411) popup image takes full width of browser window for ecommerce multiflex theme

2017-10-26 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava reassigned OFBIZ-8411:
---

Assignee: Aishwary Shrivastava

> popup image takes full width of browser window for ecommerce multiflex theme
> 
>
> Key: OFBIZ-8411
> URL: https://issues.apache.org/jira/browse/OFBIZ-8411
> Project: OFBiz
>  Issue Type: Bug
>  Components: ecommerce
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Aishwary Shrivastava
>
> go to https://localhost:8443/catalog/control/FindProductStore
> select multiflex theme
> go to ecommerce
> hover mouse over an image.
> notice that the width of popup image take width of browser window



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OFBIZ-9457) Improvements in OrderHeader entity definition and services

2017-07-08 Thread Aishwary Shrivastava (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aishwary Shrivastava updated OFBIZ-9457:

Attachment: OFBIZ-9457.diff

Here is the patch for the Improvement.
Thanks to Devanshu Vyas, Amit Gadaley, Vaibhav Jain and Rishi Solanki for the 
guidance.

Steps to verify the changes of AddItemFromOrder: 
1. Login
2.Go to Facility.
3.Go to Shipments.
4.Find an Outgoing - Sales type shipment.
5.Select the shipment.
6.Click on Order Items


Steps to verify the changes of ReceiveInventoryAgainstPurchaseOrder: 
1. Login
2.Go to Facility.
3.Go to Shipments.
4.Find an Incoming - Purchase type shipment.
5.Select the shipment.
6.Click on Receive against PO.


The data show on the screens remains same before and after applying the patch.


> Improvements in OrderHeader entity definition and services
> --
>
> Key: OFBIZ-9457
> URL: https://issues.apache.org/jira/browse/OFBIZ-9457
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Trunk
>Reporter: Rishi Solanki
>Priority: Minor
> Attachments: OFBIZ-9457.diff
>
>
> Fix entity definition of OrderHeader and do the following changes in the 
> implementation;
> - Remove relations with OrderHeaderNoteView and OrderItemAndShipGroupAssoc 
> from the entity definition.
> - Check for the both views used at any place as getRelated() generic value 
> methods on OrderHeader then change them with appropriate EntityQuery method 
> or delegaor or other script as applicable.
> - Few find areas are;
> -- AddItemsFromOrder.groovy
> -- ReceiveInventoryAgainstPurchaseOrder.groovy
> Note: As we are removing relation from OrderHeader so only need to work on 
> the items where we are trying to get related data by using the relations. We 
> need to rewrite only those lines of code. Reverse in not true.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)