[
https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496092
]
Oleg Andreyev commented on OFBIZ-796:
-------------------------------------
PMS integrated with Ofbiz, it would be great. But "aka Project Management
Application" or Project Management Application?
If last case, I'd like comment list of objectives and tasks from this jira.
> Objective -
...
> 2.> process requests in a better way,
...
> 4.> include ability to integrate seamlessly with invoices/billing ,
Enterprise resource (manufacturing) planning and project management are quite
different things in their underlying principles.
Link between task and money can be useful for some project related financial
goals but not in sense using project tasks to handling billing.
...
> 6.> send email/ mobile notifications.
> Process -
> Project Tree -
> 0 - Project/s (WE)
> 1 - Sub Project/s (WE)
What about stages (phases). Stage is not the same as sub-project.
> 2 - Task/s (WE)
3 - Sub-Task/s (WE)
-1. A task has elementary nature in project management.
> 1 - Task/s (WE) - These are not assigned to any sub-project
> 0 - Task/s - These are not assigned to any project
It makes no sense in project context.
...
> Effort -
...
> 1. Task by priority (Iteration planning), - Amit
What is the task priority in project? I don't know.
> 2 Task over time estimate,
Task finish time (start time) calculation is based on working hours (calendars)
of project itself, task, utilized resources and relations to other tasks.
So, to make this feature useful we need these entities and non trivial logic.
Otherwise we shall have improved planner only.
> 3. Project summary (By Supervisor / By Client),
> 4. Gantt for Project,
Tasks in project are organized in tree. I think we need Gantt view for each
level with permission for different kind of users.
> 7. WE estimate versus actual.
To control project flow it's very important to have possibility compare current
plan to baseline one, or any snapshots. This problem demands attention. Đ•ach
project should be looks like this tree.
Project
Project (baseline)
Project (YYYY-MM-DD)
Project (YYYY-MM-DD)
Project (current)
Tasks
> 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.
