Greetings all!
I'm a PM and I'm using ]PO[ for personal purposes in order to propose it in the future as Project Management solution for some of my customers.
I had a look at this: http://www.project-open.com/en/howto-scrum-project-management
but I found some incongruence in the last sub-paragraph "Patching the Add Release Items Page".
It says "The page packages/intranet-release-mgmt/www/add-items.tcl by default shows all release items in the system across projects. This behavior is useful for release projects, but not for SCRUM sprints. In order to fix this behaviour please patch the file and add the following text in line 162 (as a separate line just before the $where_clause line)".
Now, the .tcl mentioned file has a completely different construct close to the line 162. In fact it already contains the following:
if {$restrict_to_rel_project_p} {
set restrict_to_rel_project_sql "and tree_root_key(p.tree_sortkey) = (select tree_root_key(tree_sortkey) from im_projects where project_id = :release_project_id)"
}
So it seems to me that the file is already patched .
Correct?
Lorenzo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We're in the process of rewriting SCRUM and general agile support. There is a new package "intranet-agile" that will include a HTML 2.0 old style ("classic") Task Board + Sprint Planner to be finished before the final ]po[ V5.0 release. For ]po[ V5.1 we plan to replace this with a Sencha ExtJS JavaScript version.
So please ignore the current SCRUM HowTo at the moment and bear with us until January.
Would you like to provide us with feed-back about the usability? Then please send an email to info@project-open.com with the subject "intranet-agile", and we'll provide you with a beta version once something starts working, OK?
Cheers
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Frank,
thanks a lot for the info. I will wait for your update. About the UX, I'd be very happy to help you so I'm going to write down the email. Currently I've only set up a Debian server for personal purposes. Regarding next developments (V.5.1) , I personally don't consider the lack of a graphical front-end workframe as a minus, so no problem from my side for the moment. I'd like to write you a private note about this, just to clarify me why you choose ExtJs for the next release.
Cheers
Lorenzo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We choose Sencha ExtJS already 3 years ago as the main ]po[ JavaScript library, because of several reasons:
* It's designed for enterprise use with the Ext.Data functionalilies
* It contained the largest widget set that we were aware of. I believe this still holds. Take for example the TreeGrid that represent the "left side" of the GanttEditor.
* It even supports drag-and-drop
Anyway, this was the decision, and - so far - we're very happy with it. I don't believe there any other framework is much better.
Debian
Please make sure you double-check the CentOS installation instructions and fill in any missing part in Debian. The CentOS instructions are our default.
Cheers
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Frank,
thanks for your answer. Did not want to be inopportune with my question. It was just curiosity.
Currently Debian seems to work fine. I also modified some sql file to install some extra package that returned errors (mainly because data were already present in the tables). There 's some error that I reported as ticket in your Project SLA container, but nothing significant, at least for the moment.
Thanx a lot and have a nice evening.
Lorenzo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Greetings all!
I'm a PM and I'm using ]PO[ for personal purposes in order to propose it in the future as Project Management solution for some of my customers.
I had a look at this: http://www.project-open.com/en/howto-scrum-project-management
but I found some incongruence in the last sub-paragraph "Patching the Add Release Items Page".
It says "The page packages/intranet-release-mgmt/www/add-items.tcl by default shows all release items in the system across projects. This behavior is useful for release projects, but not for SCRUM sprints. In order to fix this behaviour please patch the file and add the following text in line 162 (as a separate line just before the $where_clause line)".
Now, the .tcl mentioned file has a completely different construct close to the line 162. In fact it already contains the following:
if {$restrict_to_rel_project_p} {
set restrict_to_rel_project_sql "and tree_root_key(p.tree_sortkey) = (select tree_root_key(tree_sortkey) from im_projects where project_id = :release_project_id)"
}
So it seems to me that the file is already patched .
Correct?
Lorenzo
Hi Lorenzo,
We're in the process of rewriting SCRUM and general agile support. There is a new package "intranet-agile" that will include a HTML 2.0 old style ("classic") Task Board + Sprint Planner to be finished before the final ]po[ V5.0 release. For ]po[ V5.1 we plan to replace this with a Sencha ExtJS JavaScript version.
So please ignore the current SCRUM HowTo at the moment and bear with us until January.
Would you like to provide us with feed-back about the usability? Then please send an email to info@project-open.com with the subject "intranet-agile", and we'll provide you with a beta version once something starts working, OK?
Cheers
Frank
Hi Frank,
thanks a lot for the info. I will wait for your update. About the UX, I'd be very happy to help you so I'm going to write down the email. Currently I've only set up a Debian server for personal purposes. Regarding next developments (V.5.1) , I personally don't consider the lack of a graphical front-end workframe as a minus, so no problem from my side for the moment. I'd like to write you a private note about this, just to clarify me why you choose ExtJs for the next release.
Cheers
Lorenzo
Hi Lorenzo,
We choose Sencha ExtJS already 3 years ago as the main ]po[ JavaScript library, because of several reasons:
* It's designed for enterprise use with the Ext.Data functionalilies
* It contained the largest widget set that we were aware of. I believe this still holds. Take for example the TreeGrid that represent the "left side" of the GanttEditor.
* It even supports drag-and-drop
Anyway, this was the decision, and - so far - we're very happy with it. I don't believe there any other framework is much better.
Please make sure you double-check the CentOS installation instructions and fill in any missing part in Debian. The CentOS instructions are our default.
Cheers
Frank
Hi Frank,
thanks for your answer. Did not want to be inopportune with my question. It was just curiosity.
Currently Debian seems to work fine. I also modified some sql file to install some extra package that returned errors (mainly because data were already present in the tables). There 's some error that I reported as ticket in your Project SLA container, but nothing significant, at least for the moment.
Thanx a lot and have a nice evening.
Lorenzo