[jira] [Assigned] (OFBIZ-10489) Unnecessary ship groups in orders
[ https://issues.apache.org/jira/browse/OFBIZ-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind Singh Tomar reassigned OFBIZ-10489: -- Assignee: (was: Arvind Singh Tomar) > Unnecessary ship groups in orders > - > > Key: OFBIZ-10489 > URL: https://issues.apache.org/jira/browse/OFBIZ-10489 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Oleg Andreyev >Priority: Minor > Fix For: Trunk > > Attachments: empty_ship_group.diff > > > Under some conditions, checkout creates extra ship groups in the order. > Steps to reproduce: > # create a couple of products P1 and P2 (just to get clear results). > # create a new order and add 1 P1 and 1 P2 > # change quantity P1 to 2 (or both) and Recalculate Order (key step really) > # finish checkout > You will see 2 order items linked with ship group 1 and another ship > group 2 that should not have been created. You may see in the patch that > the code address a ship group using index of the order item and the shopping > cart creates new ship group if the index is greater than the number of > existing groups. > In one of my projects based on 16.11, I noticed even more serious trouble > that takes place if both products are drop-shipping order but don't explain > it here because it seems do not appear in the trunk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10489) Unnecessary ship groups in orders
[ https://issues.apache.org/jira/browse/OFBIZ-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind Singh Tomar reassigned OFBIZ-10489: -- Assignee: Arvind Singh Tomar > Unnecessary ship groups in orders > - > > Key: OFBIZ-10489 > URL: https://issues.apache.org/jira/browse/OFBIZ-10489 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Oleg Andreyev >Assignee: Arvind Singh Tomar >Priority: Minor > Fix For: Trunk > > Attachments: empty_ship_group.diff > > > Under some conditions, checkout creates extra ship groups in the order. > Steps to reproduce: > # create a couple of products P1 and P2 (just to get clear results). > # create a new order and add 1 P1 and 1 P2 > # change quantity P1 to 2 (or both) and Recalculate Order (key step really) > # finish checkout > You will see 2 order items linked with ship group 1 and another ship > group 2 that should not have been created. You may see in the patch that > the code address a ship group using index of the order item and the shopping > cart creates new ship group if the index is greater than the number of > existing groups. > In one of my projects based on 16.11, I noticed even more serious trouble > that takes place if both products are drop-shipping order but don't explain > it here because it seems do not appear in the trunk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10375) Issues with Recurrence Info ID at Edit Invoice
[ https://issues.apache.org/jira/browse/OFBIZ-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind Singh Tomar updated OFBIZ-10375: --- Affects Version/s: Trunk > Issues with Recurrence Info ID at Edit Invoice > -- > > Key: OFBIZ-10375 > URL: https://issues.apache.org/jira/browse/OFBIZ-10375 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: > https://demo-trunk.ofbiz.apache.org/ap/control/updateInvoice >Reporter: Aayush jain >Priority: Major > Attachments: Screenshot from 2018-04-28 11-13-03.png > > > Steps: > 1. Open URL https://demo-trunk.ofbiz.apache.org/ap/control/updateInvoice > 2. Navigate to Edit Invoice > 3. Enter Recurrence Info ID like ABCTEST001 > 4. Check on Update button > Actual Result: > Throwing an exception error, kindly refer attachment for the same. > Expected Result: > An exception should be handled properly and the proper error message should > be displayed on the screen > Note: > Recurrence Info ID is Key of another table, so we can not enter any kind of > ramdom value. > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10375) Issues with Recurrence Info ID at Edit Invoice
[ https://issues.apache.org/jira/browse/OFBIZ-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind Singh Tomar updated OFBIZ-10375: --- Component/s: accounting > Issues with Recurrence Info ID at Edit Invoice > -- > > Key: OFBIZ-10375 > URL: https://issues.apache.org/jira/browse/OFBIZ-10375 > Project: OFBiz > Issue Type: Bug > Components: accounting > Environment: > https://demo-trunk.ofbiz.apache.org/ap/control/updateInvoice >Reporter: Aayush jain >Priority: Major > Attachments: Screenshot from 2018-04-28 11-13-03.png > > > Steps: > 1. Open URL https://demo-trunk.ofbiz.apache.org/ap/control/updateInvoice > 2. Navigate to Edit Invoice > 3. Enter Recurrence Info ID like ABCTEST001 > 4. Check on Update button > Actual Result: > Throwing an exception error, kindly refer attachment for the same. > Expected Result: > An exception should be handled properly and the proper error message should > be displayed on the screen > Note: > Recurrence Info ID is Key of another table, so we can not enter any kind of > ramdom value. > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10835) In the main interface of the HR module, when the organization structure is displayed in a tree, the name of the person is not displayed.
[
https://issues.apache.org/jira/browse/OFBIZ-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Singh Tomar reassigned OFBIZ-10835:
--
Assignee: (was: Arvind Singh Tomar)
> In the main interface of the HR module, when the organization structure is
> displayed in a tree, the name of the person is not displayed.
>
>
> Key: OFBIZ-10835
> URL: https://issues.apache.org/jira/browse/OFBIZ-10835
> Project: OFBiz
> Issue Type: Bug
> Components: humanres
>Affects Versions: 16.11.04
>Reporter: zhangqing
>Priority: Trivial
>
> HR模块的Main界面中，以树状显示组织结构时，没有显示出人员的名称
> 原因是：
> /ofbiz/applications/humanres/src/main/java/org/apache/ofbiz/humanres/HumanResEvents.java中的getCurrentEmployeeDetails方法中有2个参数错误。
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> memberId).queryOne();
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> memberId).queryOne();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10835) In the main interface of the HR module, when the organization structure is displayed in a tree, the name of the person is not displayed.
[
https://issues.apache.org/jira/browse/OFBIZ-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827508#comment-16827508
]
Arvind Singh Tomar commented on OFBIZ-10835:
[~qepkwwl], I have checked and tree structure does not show the person names
rather their designation and more detailed information can be accessed by going
through the link and opening subsequent detail pages.
If we can come up with a standard/proposed tree node information structure to
display name of the persons as well. It can be done as you have shared.
> In the main interface of the HR module, when the organization structure is
> displayed in a tree, the name of the person is not displayed.
>
>
> Key: OFBIZ-10835
> URL: https://issues.apache.org/jira/browse/OFBIZ-10835
> Project: OFBiz
> Issue Type: Bug
> Components: humanres
>Affects Versions: 16.11.04
>Reporter: zhangqing
>Assignee: Arvind Singh Tomar
>Priority: Trivial
>
> HR模块的Main界面中，以树状显示组织结构时，没有显示出人员的名称
> 原因是：
> /ofbiz/applications/humanres/src/main/java/org/apache/ofbiz/humanres/HumanResEvents.java中的getCurrentEmployeeDetails方法中有2个参数错误。
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> memberId).queryOne();
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> memberId).queryOne();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10835) In the main interface of the HR module, when the organization structure is displayed in a tree, the name of the person is not displayed.
[
https://issues.apache.org/jira/browse/OFBIZ-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Singh Tomar reassigned OFBIZ-10835:
--
Assignee: Arvind Singh Tomar
> In the main interface of the HR module, when the organization structure is
> displayed in a tree, the name of the person is not displayed.
>
>
> Key: OFBIZ-10835
> URL: https://issues.apache.org/jira/browse/OFBIZ-10835
> Project: OFBiz
> Issue Type: Bug
> Components: humanres
>Affects Versions: 16.11.04
>Reporter: zhangqing
>Assignee: Arvind Singh Tomar
>Priority: Trivial
>
> HR模块的Main界面中，以树状显示组织结构时，没有显示出人员的名称
> 原因是：
> /ofbiz/applications/humanres/src/main/java/org/apache/ofbiz/humanres/HumanResEvents.java中的getCurrentEmployeeDetails方法中有2个参数错误。
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> memberId).queryOne();
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> memberId).queryOne();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10714) Display the user selected variant product options for configurable product
[
https://issues.apache.org/jira/browse/OFBIZ-10714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Singh Tomar reassigned OFBIZ-10714:
--
Assignee: Arvind Singh Tomar
> Display the user selected variant product options for configurable product
> --
>
> Key: OFBIZ-10714
> URL: https://issues.apache.org/jira/browse/OFBIZ-10714
> Project: OFBiz
> Issue Type: Improvement
> Components: ecommerce
>Affects Versions: Trunk, 16.11.04
>Reporter: Sebastian Wachinger
>Assignee: Arvind Singh Tomar
>Priority: Major
>
> If the customer buys a configurable product, with a product component being a
> {{Product Variant}}, the selected variant (Product ID and component price) is
> displayed on the {{ConfigProductDetail}} page before you click {{Add to
> Cart}}, but after this the selected variant never is displayed, or
> communicated, at all:
> - not in the {{ShowCart}} page,
> - not in the checkout summary pages,
> - not at all in the confirmation email,
> - and not in the {{OrderInfo}} page (order detail page) in the backend
> management.
> The only way to find out which variant options the customer configured before
> buying is to click on the +{{Production Run}}+ link on the {{OrderInfo}}
> page. For the shop manager and manufacturer this might even be good enough,
> but not communicating (i.e. documenting) the ordered and sold product
> configuration in detail to the buyer spells trouble!
> So it would be great if, in the pages listed above, the selected variants
> would appear in detail, eg with the product ID of the selected variant
> product, and/or with the product name / short description, and maybe the
> component prices.
> For example, the shopping cart now only displays the lines
> {quote}Pizza
> Peppers
> Sauce
> {quote}
> Instead it should display
> {quote}Pizza
> Peppers : Roasted PEPPERS-R
> Sauce : Tomato Parmesan SAUCE-TP
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-7359) Product based promotion calculation
[ https://issues.apache.org/jira/browse/OFBIZ-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577790#comment-15577790 ] Arvind Singh Tomar commented on OFBIZ-7359: --- Resolved the merge conflicts and updated the patch. Tested the functionality and run unit tests and found out it be working fine. > Product based promotion calculation > --- > > Key: OFBIZ-7359 > URL: https://issues.apache.org/jira/browse/OFBIZ-7359 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Arvind Singh Tomar >Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7359_trunk.patch, OFBIZ-7359_trunk.patch, > Promotion1.png, Promotion2.png > > > I found the behavior of product base promotion calculation a bit strange. Any > further insights into the issue would be very helpful. > The promotion which I used was to give 30% discount for the item (i.e. > RAM1GB_BRAND). I created a sales order with 10 quantity of the product. > During the promotion calculation, OFBiz created 10 OrderAdjustments, one for > each quantity for the same promotion type. > I was expecting that in the case if same Promotion is applicable for more > than one quantity of a product then a single OrderAdjustment should be > created instead of creating one for each quantity. It is also messing up the > UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7359) Product base promotion calculation
[ https://issues.apache.org/jira/browse/OFBIZ-7359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind Singh Tomar updated OFBIZ-7359: -- Attachment: OFBIZ-7359_trunk.patch > Product base promotion calculation > -- > > Key: OFBIZ-7359 > URL: https://issues.apache.org/jira/browse/OFBIZ-7359 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Arvind Singh Tomar >Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7359_trunk.patch, OFBIZ-7359_trunk.patch, > Promotion1.png, Promotion2.png > > > I found the behavior of product base promotion calculation a bit strange. Any > further insights into the issue would be very helpful. > The promotion which I used was to give 30% discount for the item (i.e. > RAM1GB_BRAND). I created a sales order with 10 quantity of the product. > During the promotion calculation, OFBiz created 10 OrderAdjustments, one for > each quantity for the same promotion type. > I was expecting that in the case if same Promotion is applicable for more > than one quantity of a product then a single OrderAdjustment should be > created instead of creating one for each quantity. It is also messing up the > UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
