[jira] Created: (OFBIZ-796) WorkEffort Application aka Project Management Application

[Nicolas Malin (Jira)]

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

Hans Bakker commented on OFBIZ-796:
-----------------------------------

The current project manager component covers 95% of this issue. I would suggest to close it and when people feel certain parts of this issue still need attention, create a  new issue.

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Pierre Smits commented on OFBIZ-796:
------------------------------------

Before closing this, state the missing 5%. So that people can know what is out and what is in in stead of sifting through comments and code.

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Tim Ruppert commented on OFBIZ-796:
-----------------------------------

I totally agree.  Let's restate the 5% Hans, so that we can ensure that we fill in these gaps.  Since you're the most knowledgeable on this issues, please just walk thru each of the original requests and direct people to where they are implemented, or indicate that they're not, so that people can start addressing those issues.

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

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

It might good if Hans did this, but I'd say even better if other people did it to have more eyes on it, and more group understanding of what Hans has built so far, and hasn't yet built.

Comments here probably shouldn't be considered a "design" of sorts... there are conflicts in them and lots of different ideas about what project management should look like and do. We could do a design document that people edit and such, but at this point since we have a nice starting point it might be easiest and most productive for people to evaluate that and submit ideas about what to do with it.

Being a meritocracy around here what will really get implemented depends on who does the work. So, if someone wants something to work a certain way they should discuss it on the mailing list and such, but really who ever does the implementation gets to make the call. If nothing has been done before it's open water and people can roam where they want to, ie implement whatever they want. If someone thinks something should work differently than how someone else implemented it, then respect and collaboration start happening and the dev mailing list become the natural place to discuss and decide before changes are made.

Sorry, I don't know if this was necessary to write. After writing it now I look back at it and it kind of looks introductory concepts to "Interacting with an Open Source Community 101".

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Jacques Le Roux commented on OFBIZ-796:
---------------------------------------

I agree with Pierre and TIm, Hans is the most knowledgeable on this issue, hence the most able to state the 5% missing. But he has maybe not the time to work on all issues so IMHO as David suggested, interested persons should try to state this 5% as well.

BTW David, I googled for ""Interacting with an Open Source Community 101" but found nothing, what are you refering to (just curious) ?

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

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

When I mentioned others getting involved with it I wasn't worried about Hans not having enough time, more about Hans not being able to read people's minds or have access to the business experiences of other people.

About the "101" thing, I didn't mean to imply that such a thing really existed. Usually "101" refers a beginning university course, and is used colloquially to imply that concepts are very basic, and should pretty much be known and understood by everyone.

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Jacques Le Roux commented on OFBIZ-796:
---------------------------------------

Ha OK, 101 meaned nothing to me, I understand now!

Hans is very active these last times, that's why I was thinking about his time, empathy :o)

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Hans Bakker commented on OFBIZ-796:
-----------------------------------

Below the items from the original list which are not in the current Project manage application:

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),
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.

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.

Hans

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Julio Echeverria commented on OFBIZ-796:
----------------------------------------

Hello everybody,
Let me take the cordial David's invitation, and extend my congratulations for your contribution and I expect don't brake the scope but deeper the first two objectives proposed by Amid; I think that OFBiz PMA with little effort can resolve what no other ERP PM do it, because they have limited objective (inherited) to control time and resources (the process), but don't make the same with the results (the scope) and only express the completation percentage of activities.
This is because the result is (a unit) one (the classical big projects model), I think like our friend E.Poe, there is no great poem, the great poem is a successive of little poems.
1.> To make project Plan./Org. easier and intuitive
The Project tree (WBS): project, subproject, phase are nodes (as a accumulative planned/actual in phisical and monetary) to consult in any range of time.
2.> Process requests in a better way,
The Product tree (PBS): to make the tasks in cartesian product with process we can assign no only resources but requisitions of products (to buy) or services (subcontract) or results like manufacturing products, as we can associate with the workeffort application, and finally
The organization tree (OBS): When we are planning we assign generic resources ie. job positions, like chief, clerk, labourer, etc and in the schedule we have the timesheet of César Alvarez, Mike Billington, George Bush, etc,
I understand that project management scope is Services oriented, but we need at least some materials and its respective MRP for the projects (PRP). If these opinion is far of the scope sincerely excuse me

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Hans Bakker commented on OFBIZ-796:
-----------------------------------

Hi Julio,
As you already saw, there is a connection with manufacturing for the scheduling of manufacturing jobs. For this to work we need to add material and an additional type of resource with can be a machine or production street. The scheduler should take these resources also into account when calculating the most optimal schedule.
However to create a good scheduler is not easy....but at least there is a start...

Regards,
Hans

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Julio Echeverria commented on OFBIZ-796:
----------------------------------------

Hi Hans,
Thanks for your answer, that is true and I think that its is the way, I create the tasks from project application and after I access tasks from workeffort to associate requests of manufactured products, if this is the best way, your confirmation is a good news. We are testing to simplefy our MRP for project (or PRP procedure) and make the traking either in this issue or in another new in project application
Thank you very much

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Jacques Le Roux commented on OFBIZ-796:
---------------------------------------

Please what is the status of this issue, shall we close it ?

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> 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.

[Nicolas Malin (Jira)]

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

Jacques Le Roux closed OFBIZ-796.
---------------------------------

       Resolution: Later
    Fix Version/s: SVN trunk

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>             Fix For: SVN trunk
>
>         Attachments: ProjectMgr.patch
>
>
> 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.