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

Reply via email to