-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Payments to Person ID not Family ID #336
Comments
I think we do need to address this. What should it look like from a UI / Schema perspective? Should deposits be allowed to associate with both people and families? |
discussed with @crossan007 and i think a plan has been formulated |
New to CRM, was using churchinfo. So what is the plan for this and is there an ETA? |
Welcome to ChurchCRM.. I will make one last beta release for testing but we are waiting for one last security changes before we call it 2.0.0 our 1st release |
There is not yet an ETA for converting pledges to person instead of family, as there's still a little bit of debate going on about if/how it should be done. |
Thanks for the update. |
@DawoudIO Are you on board for this change? I'm more than happy to implement it, as it will fit my (and many other's) needs a lot better. Since most people will be in a family, we could still display a "Family Giving Aggregate" if desired. |
I really would love this to be flag based either person OR family. I think On Mon, Apr 4, 2016, 8:45 PM Charles notifications@github.com wrote:
|
May I ask where are we on this? |
we have held off on doing any financials in the system yet because we are waiting for this to be figured out. what do we need to do to get this going? |
I guess it would make sense for me to address this in #612. By that token - any UI input you have would be appreciated. |
I would think if we are going to allow both family and or individual could we do a double drop down? pull family first and ajax populate a second individual drop down for the individual. That would keep it clean and also speed up the list search. |
Are there any updates on this? This is the only thing stopping me from using this product |
Any update on this issue? Want to implement this platform, but I am unable to do so without this feature enabled for my org. |
@VictorPitta and @bosundare - we can appreciate the need for the change and it is being worked on (#4910). However, it is a rather significant change and we are only a small team. There is no ETA on this feature unfortunately, but we'll update this ticket when it's implemented, so all I can suggest is watch this space. Thanks for your patience 👍 |
@MrClever Thanks for getting back. Already watching it, and hopefully this feature would be available soon. |
Thanks |
I test this software around 3-4 years ago, is fantastic and the only ISSUE was exactly this, not be able to insert payments under a person instead of a family... Here I am again and I see that this has not been resolved yet, too bad, is a great software. My church is a hispanic church and I can tell you 90% of hispanic churches track finances separate in most families. |
@xtremelora - thanks for your feedback and encouragement. We are a (very) small development team and all have busy day jobs too. We know this feature would be a great improvement for a lot of users but it's actually a rather large refactor and will likely break things along the way. If you have any PHP development skills, or know someone who does, and would be willing to help out, we'd love to assist with getting a development environment set up for you and look forward to future PRs 🙂 |
Hey Team! It's been a year since the last update, any chance someone has picked this back up? The tool looks great so far and this would really make such a difference in so many lives. I look forward to your response! |
Hello everyone, I wanted to provide an update on the current status of our project. As you may have noticed, there has been little activity recently, and I wanted to explain why. At the moment, we do not have any active developers working on the project. However, we are committed to ensuring that the software remains secure and up-to-date with the latest localization improvements as people contribute them. Rest assured that we are still monitoring the project and will be available to review any pull requests that are submitted. In the meantime, we appreciate your patience and understanding The Church CRM team. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
any updates?
…On Sat, Jun 22, 2024 at 10:16 PM github-actions[bot] < ***@***.***> wrote:
This issue is stale because it has been open 30 days with no activity.
Remove stale label or comment or this will be closed in 5 days.
—
Reply to this email directly, view it on GitHub
<#336 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABXFQF3COY4J3OF62E33NLDZIYVXXAVCNFSM4B3OZ5SKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJYGQZTKNJWGMYQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Any updates on this?
…-------- Original Message --------
On 6/22/24 10:16 PM, github-actions[bot] wrote:
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
—
Reply to this email directly, [view it on GitHub](#336 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABXFQF3COY4J3OF62E33NLDZIYVXXAVCNFSM4B3OZ5SKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJYGQZTKNJWGMYQ).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
There are several reasons for this:
Married Filing Separately
Children with job tithing need to file taxes separate.
Divorcing couples might want their own records.
This also keeps household data more clean because you don't need to force new household just to make a separate giving record.
It also make the reports more private and easier to run. With the above ideas the person running the reports might need to ask too many questions to functionally get reports out in a timely manner
Any Feedback?
The text was updated successfully, but these errors were encountered: