In an environment where the software was customised to the end-user's specifications, I would expect the customer to set the priorities. The customer pays for that service.
I've worked for companies where this happened, and worked with the programmers to have bugs repaired and changes tailored to our needs, even though at the time I was a lowly office worker in the accounts department who knew next-to-nothing about programming - but knew what needed to happen in the end result. Legacy is an off-the-shelf product. People buy/download it as-is and start it running, and have limited options to customise their Legacy experience (though the options are far-ranging!). It has to be made to work effectively for thousands of people who all have their own viewpoint and priorities, and will never agree on what changes should be made, and when - and they don't pay the developer's wages. The two situations are completely different kettles of fish. Wendy Alex MacPhee said the following on 16/02/2014 1:23 a.m.: > > Anytime we say there is a problem report in our system on an issue it > > means that the programmers know of the issue. They have their own > > priority lists for when they tackle the problems so there is no knowing > > when that may be. > > In the thirty odd years I spent in IT, the priority lists for problem > reports were set by the customers, not the programmers. > > > Alex Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
