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

["Harsha Chadhar (JIRA)" <ji...@apache.org>]

     [ 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.