[jira] [Commented] (OFBIZ-11633) PartyProfileContent.js does not work

2020-05-01 Thread Mohammad Kathawala (Jira)


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

Mohammad Kathawala commented on OFBIZ-11633:


[~jleroux] The PartyProfileContent.js is indeed not used on the view profile 
page anymore. Its reference was removed in your recent commit to the file

_ofbiz-framework/trunk/applications/party/template/party/profileblocks/Content.ftl_
Here is the link to changes: 
[http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/party/template/party/profileblocks/Content.ftl?r1=1861869=1861868=1861869]

The  line '' which was removed was 
bound with the js to show the progress bar(although it does not show the 
progress bar even if the line is added back maybe because of some other 
changes). But yes, I think we can remove the reference of the js file from view 
profile screen.

> PartyProfileContent.js does not work
> 
>
> Key: OFBIZ-11633
> URL: https://issues.apache.org/jira/browse/OFBIZ-11633
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> When you upload a content from the party profile page you don't see a 
> progress bar. The PartyProfileContent.js is loaded but for some reason is 
> unused or wrong



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-7403) Allow user to select multiple options in "Purchases by Payment Method" report from basic search criterias while generating report

2020-04-27 Thread Mohammad Kathawala (Jira)


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

Mohammad Kathawala commented on OFBIZ-7403:
---

Thanks [~swash78]. I have provided a patch for #1. I think we can skip #2 for 
now as it seems a low priority and is consistent with other reports on the page.

> Allow user to select multiple options in "Purchases by Payment Method" report 
> from basic search criterias while generating report
> -
>
> Key: OFBIZ-7403
> URL: https://issues.apache.org/jira/browse/OFBIZ-7403
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: 14.12.01, 15.12.01, Trunk
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>Priority: Major
> Attachments: OFBIZ-7403.patch, Purchase_by_Payment_Method.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Payment Method' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Status
> 4) Let's convert Order type into radio button so it only work either for 
> Sales Order or for PO at one time/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-7403) Allow user to select multiple options in "Purchases by Payment Method" report from basic search criterias while generating report

2020-04-27 Thread Mohammad Kathawala (Jira)


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

Mohammad Kathawala updated OFBIZ-7403:
--
Attachment: OFBIZ-7403.patch

> Allow user to select multiple options in "Purchases by Payment Method" report 
> from basic search criterias while generating report
> -
>
> Key: OFBIZ-7403
> URL: https://issues.apache.org/jira/browse/OFBIZ-7403
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: 14.12.01, 15.12.01, Trunk
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>Priority: Major
> Attachments: OFBIZ-7403.patch, Purchase_by_Payment_Method.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Payment Method' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Status
> 4) Let's convert Order type into radio button so it only work either for 
> Sales Order or for PO at one time/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10489) Unnecessary ship groups in orders

2019-06-22 Thread Mohammad Kathawala (JIRA)


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

Mohammad Kathawala commented on OFBIZ-10489:


The issue is generated because of the code committed in the patch from the 
ticket https://issues.apache.org/jira/browse/OFBIZ-5416. Here the code was 
properly handled in _ShoppingCartEvents.java_ but not in 
_ShoppingCartHelper.java._

Did the same handling in _ShoppingCartHelper.java_  in the patch 
*OFBIZ-10489.patch*.

> 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: Mohammad Kathawala
>Priority: Minor
> Fix For: Trunk
>
> Attachments: OFBIZ-10489.patch, 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-10489) Unnecessary ship groups in orders

2019-06-22 Thread Mohammad Kathawala (JIRA)


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

Mohammad Kathawala updated OFBIZ-10489:
---
Attachment: OFBIZ-10489.patch

> 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: Mohammad Kathawala
>Priority: Minor
> Fix For: Trunk
>
> Attachments: OFBIZ-10489.patch, 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

2019-06-22 Thread Mohammad Kathawala (JIRA)


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

Mohammad Kathawala reassigned OFBIZ-10489:
--

Assignee: Mohammad Kathawala

> 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: Mohammad Kathawala
>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] [Created] (OFBIZ-10795) Product dropdown should be replaced with product lookup on Edit Price Rule screen

2019-01-11 Thread Mohammad Kathawala (JIRA)
Mohammad Kathawala created OFBIZ-10795:
--

 Summary: Product dropdown should be replaced with product lookup 
on Edit Price Rule screen
 Key: OFBIZ-10795
 URL: https://issues.apache.org/jira/browse/OFBIZ-10795
 Project: OFBiz
  Issue Type: Improvement
  Components: product
Affects Versions: Release Branch 16.11, Trunk, Release Branch 17.12
Reporter: Mohammad Kathawala
Assignee: Pradeep Choudhary
 Fix For: Release Branch 17.12, Release Branch 16.11, Trunk


On Edit Price Rule screen, all the products of the system are fetched in a 
single dropdown.

If a system has thousands or more products, then it will take too much time to 
load those products in the dropdown and screen loading time will increase or 
even it can make the system down.

 

We should have a product lookup here.



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


[jira] [Commented] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

2018-04-28 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala commented on OFBIZ-7713:
---

[~swash78] , I think we should keep the 'PartyId To' empty only. There can be 
multiple product stores and multiple internal organizations in the system. I 
have added patch for showing now time stamp in from date field. I think we can 
close this task after committing the recent patch.

 

Thanks.

> Introduce a quick way for adding Sales Price agreements with customers for 
> any specific product from Catalog
> 
>
> Key: OFBIZ-7713
> URL: https://issues.apache.org/jira/browse/OFBIZ-7713
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>Priority: Major
> Attachments: OFBIZ-7713.patch, OFBIZ-7713.patch, SPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From
> #- Party Id To (Default it to product store's owner party id)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> # Upon successful submission of above details system should create Agreement 
> and Agreement Item between customer and organization by passing following 
> default values:
> #- Role Type Id From = 'Customer'
> #- Role Type Id To = 'Internal Organization'
> #- Agreement Type Id = 'Sales'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



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


[jira] [Updated] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

2018-04-28 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7713:
--
Attachment: OFBIZ-7713.patch

> Introduce a quick way for adding Sales Price agreements with customers for 
> any specific product from Catalog
> 
>
> Key: OFBIZ-7713
> URL: https://issues.apache.org/jira/browse/OFBIZ-7713
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>Priority: Major
> Attachments: OFBIZ-7713.patch, OFBIZ-7713.patch, SPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From
> #- Party Id To (Default it to product store's owner party id)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> # Upon successful submission of above details system should create Agreement 
> and Agreement Item between customer and organization by passing following 
> default values:
> #- Role Type Id From = 'Customer'
> #- Role Type Id To = 'Internal Organization'
> #- Agreement Type Id = 'Sales'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



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


[jira] [Updated] (OFBIZ-10004) Error in Create Billing Account from Party Profile

2017-11-24 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-10004:
---
Issue Type: Sub-task  (was: Bug)
Parent: OFBIZ-7208

> Error in Create Billing Account from Party Profile
> --
>
> Key: OFBIZ-10004
> URL: https://issues.apache.org/jira/browse/OFBIZ-10004
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: party
>Affects Versions: Release Branch 16.11
>Reporter: Mohammad Kathawala
>
> Steps to generate:
> 1) Go to Create Billing Account from Party Profile.
> 2) Fill the form and click on save. It will give an error of request not 
> found.



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


[jira] [Created] (OFBIZ-10004) Error in Create Billing Account from Party Profile

2017-11-24 Thread Mohammad Kathawala (JIRA)
Mohammad Kathawala created OFBIZ-10004:
--

 Summary: Error in Create Billing Account from Party Profile
 Key: OFBIZ-10004
 URL: https://issues.apache.org/jira/browse/OFBIZ-10004
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Release Branch 16.11
Reporter: Mohammad Kathawala


Steps to generate:

1) Go to Create Billing Account from Party Profile.
2) Fill the form and click on save. It will give an error of request not found.



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


[jira] [Updated] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

2016-09-22 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7713:
--
Attachment: OFBIZ-7713.patch

Added patch with following changes:

1) Added new screen for Create Sales Agreement form in ProductScreens.xml
2) Added new link on View Product Agreements screen of Create Sales Agreement 
to redirect user to the form and also added controller request for the same.
3) Added Create Sales Agreement form in ProductForms.xml mentioned fields in 
the ticket.
4) Added a group service called createSalesAgreement which contains 3 services: 
i) createAgreement ii) createAgreementItem iii) createAgreementProductAppl. 
Added new groups.xml file in product/servicedef.
5) Added a controller request on submitting the form which will call the group 
service.

> Introduce a quick way for adding Sales Price agreements with customers for 
> any specific product from Catalog
> 
>
> Key: OFBIZ-7713
> URL: https://issues.apache.org/jira/browse/OFBIZ-7713
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7713.patch, SPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From
> #- Party Id To (Default it to product store's owner party id)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> # Upon successful submission of above details system should create Agreement 
> and Agreement Item between customer and organization by passing following 
> default values:
> #- Role Type Id From = 'Customer'
> #- Role Type Id To = 'Internal Organization'
> #- Agreement Type Id = 'Sales'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

2016-09-22 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala reassigned OFBIZ-7713:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Introduce a quick way for adding Sales Price agreements with customers for 
> any specific product from Catalog
> 
>
> Key: OFBIZ-7713
> URL: https://issues.apache.org/jira/browse/OFBIZ-7713
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: SPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From
> #- Party Id To (Default it to product store's owner party id)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> # Upon successful submission of above details system should create Agreement 
> and Agreement Item between customer and organization by passing following 
> default values:
> #- Role Type Id From = 'Customer'
> #- Role Type Id To = 'Internal Organization'
> #- Agreement Type Id = 'Sales'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

2016-09-19 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7543:
--
Attachment: OFBIZ-7543-return.patch

Added missing patch for Find Return Screen.

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Order' component
> ---
>
> Key: OFBIZ-7543
> URL: https://issues.apache.org/jira/browse/OFBIZ-7543
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7543-return.patch, OFBIZ-7543.patch
>
>
> Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7550) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Project' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7550:
--
Attachment: OFBIZ-7550.patch

Added checkbox for status fields on
Find Tasks
Find TimeSheet

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Project' component
> -
>
> Key: OFBIZ-7550
> URL: https://issues.apache.org/jira/browse/OFBIZ-7550
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: specialpurpose/projectmgr
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7550.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7549) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'HR' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7549:
--
Attachment: OFBIZ-7549.patch

Added checkbox for status fields on
Find Qualifications
Find Employment Applications
Find Leave

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'HR' component
> 
>
> Key: OFBIZ-7549
> URL: https://issues.apache.org/jira/browse/OFBIZ-7549
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7549.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7548) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'WorkEffort' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7548:
--
Attachment: OFBIZ-7548.patch

Added checkbox for status fields on Find Work Effort Screen.


> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'WorkEffort' component
> 
>
> Key: OFBIZ-7548
> URL: https://issues.apache.org/jira/browse/OFBIZ-7548
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: workeffort
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7548.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7547) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Content' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7547:
--
Attachment: OFBIZ-7547.patch

Added checkbox for status fields on
Find Content
Find Data Resource

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Content' component
> -
>
> Key: OFBIZ-7547
> URL: https://issues.apache.org/jira/browse/OFBIZ-7547
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7547.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7543:
--
Attachment: OFBIZ-7543.patch

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Order' component
> ---
>
> Key: OFBIZ-7543
> URL: https://issues.apache.org/jira/browse/OFBIZ-7543
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7543.patch
>
>
> Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7543:
--
Attachment: (was: OFBIZ-7543.patch)

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Order' component
> ---
>
> Key: OFBIZ-7543
> URL: https://issues.apache.org/jira/browse/OFBIZ-7543
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>
> Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OFBIZ-7545) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Facility' component

2016-09-17 Thread Mohammad Kathawala (JIRA)

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

Mohammad Kathawala updated OFBIZ-7545:
--
Attachment: OFBIZ-7545.patch

Added checkbox for status fields on
Find Inventory Items
Find Shipment

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Facility' component
> --
>
> Key: OFBIZ-7545
> URL: https://issues.apache.org/jira/browse/OFBIZ-7545
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7545.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)