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. |
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495689 ] Adrian Crum commented on OFBIZ-796: ----------------------------------- Would we want to address the timezone/locale issues while we're working on this? > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495693 ] Adrian Crum commented on OFBIZ-796: ----------------------------------- Would this be a separate webapp? Do we create new folders in the Workeffort component? Maybe a good first step would be to commit a folder structure that everyone can work off of. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495698 ] Anil K Patel commented on OFBIZ-796: ------------------------------------ I think we should create a webapp "projectmgr" in workeffort component. If other are fine with this, I'll create initial files and upload the patch. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495708 ] Amit Shinde commented on OFBIZ-796: ----------------------------------- I had created a Reports Screen which was supposed to be a placeholder for all the reports that we had slated to implement. I will upload the patch late tonight PST. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495714 ] Amit Shinde commented on OFBIZ-796: ----------------------------------- I dont think we need a new webapp at present. Its too nascent of a stage right now. We should focus on the reports which can still stay under workeffort. When we have a bunch of functionality which separates from workeffort, then we could move it out. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495721 ] Tim Ruppert commented on OFBIZ-796: ----------------------------------- My vote would be to have another Component. This is a project that has a lot of interest and I think should be pushed accordingly. My two cents > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495726 ] Anil K Patel commented on OFBIZ-796: ------------------------------------ If its component then I think it should go in specialpurpose folder, because it may use artifacts from WorkEffort, Party, Order etc. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495735 ] Amit Shinde commented on OFBIZ-796: ----------------------------------- I might be missing some information. Can we list/scope all the future things that will be going/done in the new webapp. As per the above tasks, which revolve mainly around reports, it may seem an overkill. My 1 cent. I already gave my 1 cent before :) > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495744 ] Adrian Crum commented on OFBIZ-796: ----------------------------------- The "Objective" items 1 to 4 would seem to require some UI work. That's why I asked about the webapp. I picture it as being a few additional screens and the reports - which (IMO) would belong in the Workeffort component. In other words, we're still using the Workeffort component, but we're adding a Project Manager "skin" to it. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ 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. |
In reply to this post by Nicolas Malin (Jira)
[ 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498065 ] Si Chen commented on OFBIZ-796: ------------------------------- A couple of suggestions: 1. Could you use the existing workEffortTypeId, TASK, for the project or at least its assignable sub-tasks? 2. I think one problem with web-based issue trackers is that the UI is slow. It'd be much nicer to have something that worked like a spreadsheet, so all the tasks are shown in a grid of Task, Client, Status, Assignnee, etc. Then you can go to a column called "Comments" and then scroll up and down and add your comments at the end. There should be some filtering at the top for the fields. The other thing that'd be great is to have the grid be "live" in the browser and persist the entire grid at once only when the user clicks on "Save". This will make it much more user friendly and useful than the existing issue tracking systems. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498467 ] Shi Yusen commented on OFBIZ-796: --------------------------------- Great. With Oleg's comment, this tool will be great for us. I plan to pass CMM 4 in 3 years and I need this tool to accumulate and analyse our data. Has anybody started this development? > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498478 ] Amit Shinde commented on OFBIZ-796: ----------------------------------- Nothing has started yet. But I hope to get this moving pretty soon. I am going to start with creating some test data for reports and a few base screens. We can then start implementing the reports mentioned above. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil K Patel reassigned OFBIZ-796: ---------------------------------- Assignee: Anil K Patel > 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 > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil K Patel updated OFBIZ-796: ------------------------------- Attachment: ProjectMgr.patch Initial setup for ProjectMgr component in special purpose folder. Next few days I'll add more items to it. Please review and give feedback. > 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 > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501209 ] Shi Yusen commented on OFBIZ-796: --------------------------------- Here is a tool which can make the workeffort report charming: Source code: http://sourceforge.net/projects/jfreechart Sample: http://www.jfree.org/jfreechart/samples.html > 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 > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501219 ] Jacques Le Roux commented on OFBIZ-796: --------------------------------------- Shi, Interesting but just as an external addon : GPL licenced hence not compatible with ASL2. > 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 > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647881#action_12647881 ] Jacques Le Roux commented on OFBIZ-796: --------------------------------------- Is this still intended to be commited or has the new component totally replaced this effort ? > 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. |
Free forum by Nabble | Edit this page |