[jira] Created: (OFBIZ-1852) Enhancement in ProjectMgr and WorkEffort component

[Nicolas Malin (Jira)]

Enhancement in ProjectMgr and WorkEffort component
--------------------------------------------------

                 Key: OFBIZ-1852
                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
             Project: OFBiz
          Issue Type: Improvement
          Components: specialpurpose/projectmgr
            Reporter: Ashish Vijaywargiya
            Priority: Trivial


1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
Add a Text Field by heading "Party Id" and put the search party lookup for it.
Also add the "Party Id" field in the list displayed at the bottom.
Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.

2) Add New Entity WorkEffortHistory.
Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
We didn't find WorkEffortNote entity useful for this purpose.

3) From Project Summary Screen :-
Divide the Resource screen into two parts :-
1) Member Involved
2) Client Personnel

This will provide easy way of handling resources to navigate from the Project Summary Screen.

--
Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

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

Ashish Vijaywargiya reassigned OFBIZ-1852:
------------------------------------------

    Assignee: Ashish Vijaywargiya

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

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

Harsha Chadhar updated OFBIZ-1852:
----------------------------------

    Attachment: ProjectMgr.patch

1.Created Entity WorkEffortHistory.
2.Added PartyId to the FindProject Screen to search the projects associated with the Parties(Clients or Members).The Entity now used to search the records has been replaced to WorkEffortPartyAssignment.
3.Added PartyId,RoleTypeId,StatusId etc that display the Project and their associated Resources(Parties that could be of RoleType Client or Members involved) to the ListProjects.
4.The ProjectView now displays the list of Client Personnel and Members Involved(Resources) seperatly with a link to view their profile.

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>         Attachments: ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608436#action_12608436 ]

David E. Jones commented on OFBIZ-1852:
---------------------------------------

Why add the WorkEffortHistory entity when the WorkEffortStatus entity already exists and covers the same need?

Please don't commit this until this question has been resolved.

-David

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>         Attachments: ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608459#action_12608459 ]

Ashish Vijaywargiya commented on OFBIZ-1852:
--------------------------------------------

David,

Thanks for your comment.

I will look at the WorkEffortStatus table tomorrow and try to find the way from it.
Somehow I missed that entity so sorry for that.

--
Ashish

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>         Attachments: ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

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

parimal gain updated OFBIZ-1852:
--------------------------------

    Attachment: ProjectMgr.patch

Uploaded patch on behalf of Harsha for #3 .
I have reviewed the patch and it is working fine.

Thanks to Ratnesh Upadhyay for his support.

Thanks & Regards
- Parimal Gain

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>         Attachments: ProjectMgr.patch, ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

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

Harsha Chadhar updated OFBIZ-1852:
----------------------------------

    Attachment: ProjectMgr.patch

Corrected the ViewProfile Display problem of the clients and Providers in the ProjectView Screen.
Thanks Ratnesh for the Support

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>         Attachments: ProjectMgr.patch, ProjectMgr.patch, ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

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

Hans Bakker closed OFBIZ-1852.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: SVN trunk

Do we still need this?

1: has the problem, tha when somebody is member of of a project in 2 roles, the project is listed twice.
2: entity already there.
3: the list of parties already show the clients and provider parties, so is there really a need to split that up?

Regards,
Hans

> Enhancement in ProjectMgr and WorkEffort component
> --------------------------------------------------
>
>                 Key: OFBIZ-1852
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1852
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: specialpurpose/projectmgr
>            Reporter: Ashish Vijaywargiya
>            Assignee: Ashish Vijaywargiya
>            Priority: Trivial
>             Fix For: SVN trunk
>
>         Attachments: ProjectMgr.patch, ProjectMgr.patch, ProjectMgr.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> 1) Update the FindProject screen to use WorkEffortAndPartyAssignment entity instead of WorkEffort to display the associated party(that can be a client) list with the Project (aka WorkEffort).
> Add a Text Field by heading "Party Id" and put the search party lookup for it.
> Also add the "Party Id" field in the list displayed at the bottom.
> Party Id can be used to display resources i.e it can be either Client or Member who is assigned to work on the Project.
> 2) Add New Entity WorkEffortHistory.
> Reason :- When we update the Status of workeffort then in case of Hold and Cancel the reason should be specified.
> We can put the Reason into Description field.And the description associated with status can be maintained in WorkEffortHistory entity.
> We didn't find WorkEffortNote entity useful for this purpose.
> 3) From Project Summary Screen :-
> Divide the Resource screen into two parts :-
> 1) Member Involved
> 2) Client Personnel
> This will provide easy way of handling resources to navigate from the Project Summary Screen.
> --
> Ashish & Ratnesh

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.