[
https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496204
]
David E. Jones commented on OFBIZ-796:
--------------------------------------
Of the various options I most like the idea of keeping things simple and adding
them to existing applications, mostly the WorkEffort Manager for now.
The idea of a Project Manager Application is interesting, but what we're
talking about is scoped a bit beyond just managing projects, it is really a
much more robust work management and client interaction system, well and
worker/manager interaction system too.
The only place I see we need a new webapp, which can probably go into the
WorkEffort component, but maybe should go into a new component in the
specialpurpose directory, is for roles that have specific needs that we may not
want to have access to all of the WorkEffort Manager functionality, namely:
1. clients (create, view requests, view and comment on work efforts, see
certain reports, etc)
2. employees and contractors (view requests, view work efforts, update their
own status on work efforts (but not necessary status of the work effort
itself), and so on with perhaps a few variations based on permissions or roles
related to a root work effort for a larger item)
> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
> Key: OFBIZ-796
> URL: https://issues.apache.org/jira/browse/OFBIZ-796
> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: workeffort
> Reporter: Amit Shinde
>
> WorkEffort Application aka Project Management Application -
> Objective -
> 1.> make project planning/organization easier and intuitive,
> 2.> process requests in a better way,
> 3.> improve iteration planning,
> 4.> include ability to integrate seamlessly with invoices/billing ,
> 5.> generate detailed and snappy reports,
> 6.> send email/ mobile notifications.
> Process -
> Project Tree -
> 0 - Project/s (WE)
> 1 - Sub Project/s (WE)
> 2 - Task/s (WE)
> 3 - Sub-Task/s (WE)
> 1 - Task/s (WE) - These are not assigned to any sub-project
> 0 - Task/s - These are not assigned to any project
> 0 - Request/s-
> 1 - Request Item/s
> - Projects, Sub-projects and Tasks all are WorkEfforts of a respective type.
> - Request is a CustRequest and can have many Request Items.
> - Time Entry can be done from any level or type of WE
> - Requests and WorkEfforts have many-to-many relationship
> Effort -
> Most of the screens and models are already in place. We definitely dont need
> any changes in the models. We need to add new screens, forms and services.
> Heres a list of todos -
> Create Demo data of a project - I am working on this one right now. This will
> be helpful for reports. We can import this and pick any of the reports and
> start implement them.
> Create Reports Menu page - Adrian Crum has helped with this.
> Reports - These are planned to be pdfs but to start with we can start
> implementing them in HTML.
> 1. Task by priority (Iteration planning), - Amit
> 2 Task over time estimate,
> 3. Project summary (By Supervisor / By Client),
> 4. Gantt for Project,
> 5. Tasks of type project,
> 6. Tasks completed, times task was reopened, Avg. time taken to fix a task
> , Avg. number of tasks fixed per day, - Amit
> 7. WE estimate versus actual.
> UI - All these screens will be in HTML.
> 1. Tasks assigned to me, - Amit
> 2. Tasks not assigned, dropdown/popup assign to X
> 3. Tasks not scheduled
> 4. Tasks past schedule
> 5. Estimated schedule/ workload for me
> Email notifications -
> 1. Tasks assigned to me
> 2. Weekly project summary
> Mobile Notifications -
> 1. Send SMS alert on any event. - Need to do more research.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
