<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Creative Project Management Software Blog | Copper Project</title>
	<atom:link href="http://www.copperproject.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.copperproject.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 18 Sep 2010 06:23:52 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by admin</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-228</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 18 Sep 2010 06:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-228</guid>
		<description>HI Boris,

Clients module is gone for v5, but in its place will be a functionality that allows you to overview projects per organization anyway.. We really really really need to simplify this area and as scary as the change may seem to you now, know that our biggest fear is removing stuff that is going to make Copper LESS popular ;) Still early days yet, but the theory we&#039;re sharing now is designed to generate discussion, and as we move closer to being able to show customers the proposed changes, we&#039;ll be able to lock down exactly what the changes will be.

Its big, fat, hairy, audacious, but so was the iphone. Thats the kind of market-leading efficiency we want to finally bring with v5. Months away I&#039;d say too, so plenty of time to get it right.</description>
		<content:encoded><![CDATA[<p>HI Boris,</p>
<p>Clients module is gone for v5, but in its place will be a functionality that allows you to overview projects per organization anyway.. We really really really need to simplify this area and as scary as the change may seem to you now, know that our biggest fear is removing stuff that is going to make Copper LESS popular <img src='http://www.copperproject.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Still early days yet, but the theory we&#8217;re sharing now is designed to generate discussion, and as we move closer to being able to show customers the proposed changes, we&#8217;ll be able to lock down exactly what the changes will be.</p>
<p>Its big, fat, hairy, audacious, but so was the iphone. Thats the kind of market-leading efficiency we want to finally bring with v5. Months away I&#8217;d say too, so plenty of time to get it right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by admin</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-227</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 18 Sep 2010 06:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-227</guid>
		<description>Thanks Simon, rest assured the data integrity isn&#039;t compromised, we&#039;ve been cooking up a really powerful structure over here, I think its going to allow the flexibility and control that most if not all of our customers want.</description>
		<content:encoded><![CDATA[<p>Thanks Simon, rest assured the data integrity isn&#8217;t compromised, we&#8217;ve been cooking up a really powerful structure over here, I think its going to allow the flexibility and control that most if not all of our customers want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by Simon James</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-223</link>
		<dc:creator>Simon James</dc:creator>
		<pubDate>Fri, 17 Sep 2010 23:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-223</guid>
		<description>The statement &quot;Anyone can create an Organization or a Project...&quot; concerns me greatly, and I hope I have misunderstood what you are saying.
Having been an implementation consultant for 14 years for one of the most flexible and powerful ERP systems ever created, I know only too well the dangers of giving users the unconstrained ability to create and amend static data records (e.g. project codes, item codes, transaction types, people) without the need for authorisation.
Most of troubleshooting I have had to do was not down to lack of functionality, it was because people created such records oblivious to the fact that they are at odds with crucial systems process or business logic, or contra to a predetermined coding structure.
They then happily start posting transactions or performing process tasks linked to this rogue data until someone notices a problem - usually when their reports start going ga ga, or users get access to data that they shouldn&#039;t do.
In short, the majority of users should have (and only want) just enough permissions and options on the system to enable them to perform their role-specific tasks. For example, purchasing departments should be able to set up supplier records, but not customer records; project managers can set up projects, but not chart of accounts records; lawyers should... uhm... well just chuck themselves under a bus ;-)
I certainly couldn&#039;t allow clients onto a system where they are free to start creating their own projects etc. And I&#039;m pretty certain they would regard with suspicion, the security of any system that seemingly allows anybody to set up any record they like.
As I say, I hope I misunderstood; because what I need are systems where one or two &quot;super users&quot; are in charge of the creation and maintenance of reference data, and everyone else (clients, outsourced workers, trainees, part-timers, untrained users, etc.) can just get on with completing the tasks assigned to them.</description>
		<content:encoded><![CDATA[<p>The statement &#8220;Anyone can create an Organization or a Project&#8230;&#8221; concerns me greatly, and I hope I have misunderstood what you are saying.<br />
Having been an implementation consultant for 14 years for one of the most flexible and powerful ERP systems ever created, I know only too well the dangers of giving users the unconstrained ability to create and amend static data records (e.g. project codes, item codes, transaction types, people) without the need for authorisation.<br />
Most of troubleshooting I have had to do was not down to lack of functionality, it was because people created such records oblivious to the fact that they are at odds with crucial systems process or business logic, or contra to a predetermined coding structure.<br />
They then happily start posting transactions or performing process tasks linked to this rogue data until someone notices a problem &#8211; usually when their reports start going ga ga, or users get access to data that they shouldn&#8217;t do.<br />
In short, the majority of users should have (and only want) just enough permissions and options on the system to enable them to perform their role-specific tasks. For example, purchasing departments should be able to set up supplier records, but not customer records; project managers can set up projects, but not chart of accounts records; lawyers should&#8230; uhm&#8230; well just chuck themselves under a bus <img src='http://www.copperproject.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
I certainly couldn&#8217;t allow clients onto a system where they are free to start creating their own projects etc. And I&#8217;m pretty certain they would regard with suspicion, the security of any system that seemingly allows anybody to set up any record they like.<br />
As I say, I hope I misunderstood; because what I need are systems where one or two &#8220;super users&#8221; are in charge of the creation and maintenance of reference data, and everyone else (clients, outsourced workers, trainees, part-timers, untrained users, etc.) can just get on with completing the tasks assigned to them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by Boris</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-220</link>
		<dc:creator>Boris</dc:creator>
		<pubDate>Thu, 16 Sep 2010 20:35:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-220</guid>
		<description>It&#039;s OK to make it simpler, but PLEASE don&#039;t take away the CLIENTS module - it&#039;s a really nice overview of the project portfolio. You could possibly make the PROJECTS view more advanced (add filtering and maybe the ability to choose wich data columns to show (like &quot;project owner&quot;, &quot;activity&quot;, ...)), but untill then I would really like to keep the CLEINTS module.</description>
		<content:encoded><![CDATA[<p>It&#8217;s OK to make it simpler, but PLEASE don&#8217;t take away the CLIENTS module &#8211; it&#8217;s a really nice overview of the project portfolio. You could possibly make the PROJECTS view more advanced (add filtering and maybe the ability to choose wich data columns to show (like &#8220;project owner&#8221;, &#8220;activity&#8221;, &#8230;)), but untill then I would really like to keep the CLEINTS module.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by Dee Baker</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-219</link>
		<dc:creator>Dee Baker</dc:creator>
		<pubDate>Thu, 16 Sep 2010 20:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-219</guid>
		<description>Sounds like some good changes.  One thing that would help us a lot is to be able to assign a Supervisor for a person.  We have many projects where the project owner is not necessarily the resource&#039;s Supervisor.  Because the Supervisor needs to ensure his people are fully utilized he needs to see the tasks his people have assigned to them.  Also that supervisor would want to run reports to see what projects his people worked on during the last week or month.  It&#039;s a whole lot easier if he can select his group of people rather than do it individually or by project.</description>
		<content:encoded><![CDATA[<p>Sounds like some good changes.  One thing that would help us a lot is to be able to assign a Supervisor for a person.  We have many projects where the project owner is not necessarily the resource&#8217;s Supervisor.  Because the Supervisor needs to ensure his people are fully utilized he needs to see the tasks his people have assigned to them.  Also that supervisor would want to run reports to see what projects his people worked on during the last week or month.  It&#8217;s a whole lot easier if he can select his group of people rather than do it individually or by project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by Carlos Garcia</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-200</link>
		<dc:creator>Carlos Garcia</dc:creator>
		<pubDate>Sat, 11 Sep 2010 21:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-200</guid>
		<description>I just started testing Copper (currently using basecamp, looking fwd to change). I like what I see and these changes make sense to me. When and where can we test this new version?

Great work Ben!
Thanks,
Carlos</description>
		<content:encoded><![CDATA[<p>I just started testing Copper (currently using basecamp, looking fwd to change). I like what I see and these changes make sense to me. When and where can we test this new version?</p>
<p>Great work Ben!<br />
Thanks,<br />
Carlos</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by admin</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-190</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 08 Sep 2010 00:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-190</guid>
		<description>Hi Pierre,

I&#039;m actually going to edit this post above, firstly changing &#039;groups&#039; to &#039;organization&#039;, and also introducing the merging of Clients/Groups into &#039;Organization&#039;. I&#039;ll explain why above, but effectively we&#039;re going to simplify even further.

The categories you refer to above will simply be a Person/Organization &#039;Type&#039;. So an Organization can be &#039;MyCompany&#039; or it can be &#039;ACME client&#039; or it can be &#039;Marketing Department&#039; or it can be &#039;Special Project Team A&#039;. Similarly a Person can be a contact, or if you select to allow them to log in, then you can set their access permissions and they become a user. So you can have unlimited &#039;People&#039; in copper, and your license limit is on the number of People-who-can-log-in (e.g. Standard would allow 5 People to log in.)

All projects relate to one Organization, All people belong to one or many Organizations. Access is managed at the Organization and Person level (and we have a separate area for switching on/off modules). 

We&#039;re excited about the change, while it will take a little getting used to, it provides a FAR simpler and usable product. I&#039;ll post back with some screenshots and we should have a beta in a few weeks.</description>
		<content:encoded><![CDATA[<p>Hi Pierre,</p>
<p>I&#8217;m actually going to edit this post above, firstly changing &#8216;groups&#8217; to &#8216;organization&#8217;, and also introducing the merging of Clients/Groups into &#8216;Organization&#8217;. I&#8217;ll explain why above, but effectively we&#8217;re going to simplify even further.</p>
<p>The categories you refer to above will simply be a Person/Organization &#8216;Type&#8217;. So an Organization can be &#8216;MyCompany&#8217; or it can be &#8216;ACME client&#8217; or it can be &#8216;Marketing Department&#8217; or it can be &#8216;Special Project Team A&#8217;. Similarly a Person can be a contact, or if you select to allow them to log in, then you can set their access permissions and they become a user. So you can have unlimited &#8216;People&#8217; in copper, and your license limit is on the number of People-who-can-log-in (e.g. Standard would allow 5 People to log in.)</p>
<p>All projects relate to one Organization, All people belong to one or many Organizations. Access is managed at the Organization and Person level (and we have a separate area for switching on/off modules). </p>
<p>We&#8217;re excited about the change, while it will take a little getting used to, it provides a FAR simpler and usable product. I&#8217;ll post back with some screenshots and we should have a beta in a few weeks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming Soon &#8211; People! (Lets merge Clients, Users, Groups, Contacts) by Pierre AMEZCUA</title>
		<link>http://www.copperproject.com/blog/2010/09/05/coming-soon-people-lets-merge-clients-users-groups-contacts/comment-page-1/#comment-189</link>
		<dc:creator>Pierre AMEZCUA</dc:creator>
		<pubDate>Tue, 07 Sep 2010 18:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=322#comment-189</guid>
		<description>Hi Ben,
simplifying is always good. Since I am not sure to understand the complete scope of your work, her is a comment of what we currently need:

beside user, and groups, we would need categories like Client, Contractor, Employee

The reason why these categories would be a plus is to allocate work or projects to outside users

Thanks

Pierre</description>
		<content:encoded><![CDATA[<p>Hi Ben,<br />
simplifying is always good. Since I am not sure to understand the complete scope of your work, her is a comment of what we currently need:</p>
<p>beside user, and groups, we would need categories like Client, Contractor, Employee</p>
<p>The reason why these categories would be a plus is to allocate work or projects to outside users</p>
<p>Thanks</p>
<p>Pierre</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Version Out Now, v4.4! by admin</title>
		<link>http://www.copperproject.com/blog/2010/07/22/project-software-copper-4/comment-page-1/#comment-77</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 23 Jul 2010 18:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=295#comment-77</guid>
		<description>Thanks Josh. This is the first we&#039;ve heard of troubles so we&#039;ll be in touch via email to work with you on a resolution!

Travis</description>
		<content:encoded><![CDATA[<p>Thanks Josh. This is the first we&#8217;ve heard of troubles so we&#8217;ll be in touch via email to work with you on a resolution!</p>
<p>Travis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Version Out Now, v4.4! by Joshua Huisenga</title>
		<link>http://www.copperproject.com/blog/2010/07/22/project-software-copper-4/comment-page-1/#comment-76</link>
		<dc:creator>Joshua Huisenga</dc:creator>
		<pubDate>Fri, 23 Jul 2010 18:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.copperproject.com/blog/?p=295#comment-76</guid>
		<description>The alert is great, except that the little closing &quot;x&quot; doesn&#039;t work, so I can&#039;t get rid of the alert.</description>
		<content:encoded><![CDATA[<p>The alert is great, except that the little closing &#8220;x&#8221; doesn&#8217;t work, so I can&#8217;t get rid of the alert.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

