RoadmapThis is a draft plan for future development of the Nonprofit Starter Pack. Release Spring 10 - Planning- Issues
- exception handing
- minimize test failures on install upgrade (existing Individual Account)
- campaigns in recurring donations
- translation improvements to Recurring Donations
- Technical documentation v.2
- Lead convert 1-to-1 model, v.2
- Incorporation of Winter '10 advancements
- UI improvements to Contact Merge
Release Winter 10 - released 11/05/2009- Issues
- better Lead Conversion (dealing with email and phone)
- ContactMerge for the 1-to-1 model
Release #2 - released 09/11/09- Issues
- Test coverage improvements
- Tests for bulk data scenarios
- Minimize pre/post install steps
- Spanish Translations
Release #1 - released 06/15/09- Open Sourcing
- New wiki
- Test coverage improvements
|
Sign in to add a comment
Steve . .your awesome! Just a thought . . maybe the merge issue could be prioritized over the pre/post install steps. For a NP using a consultant, or an average techie the pre/post is not such an issue, but the merging is a huge headache. Just my $.02 . . . Thanks for all your hard work!
Point taken. Because Contact merge is a larger project, I moved it out one release. I'm in the midst of Release 2 now, so we're not far from the Contact merge functionality, I think.
Any idea when the bug between household address and contact address will be fixed? Although the addresses are matched on creation future changes have to be made on both the contact and household objects, thus quickly getting out of sync. This is not only a royal PITA, it's a significant data integrity problem.
I agree that it would be better to have contact and household addresses in sync. Having built this exact functionality before, I do know that it is actually very complex and may not even be possible in the constraints of the Nonprofit Starter Pack. I'll see if I can fit the analysis of the problem into the next few months of work.