Skip to content
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

Open
rakess70 opened this issue Feb 17, 2016 · 33 comments
Open

Move Payments to Person ID not Family ID #336

rakess70 opened this issue Feb 17, 2016 · 33 comments

Comments

@rakess70
Copy link

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?

@crossan007
Copy link
Contributor

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?

@rakess70
Copy link
Author

discussed with @crossan007 and i think a plan has been formulated

@gyphon
Copy link

gyphon commented Apr 3, 2016

New to CRM, was using churchinfo. So what is the plan for this and is there an ETA?
thanks, Larry

@DawoudIO
Copy link
Contributor

DawoudIO commented Apr 4, 2016

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

@crossan007
Copy link
Contributor

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.

@gyphon
Copy link

gyphon commented Apr 4, 2016

Thanks for the update.
My treasurer is telling me that the IRS requires each tax payer to have a separate letter of givings. Churchinfo ans to this was to create each person as a family. To me this would defeat the purpose of having a family group.
Please keep me in the loop as this will be a make-break for us.
Larry

@DawoudIO DawoudIO added this to the 2.1.0 milestone Apr 4, 2016
@crossan007
Copy link
Contributor

@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.

@dschwen
Copy link

dschwen commented Apr 5, 2016

I really would love this to be flag based either person OR family. I think
this should be doable.

On Mon, Apr 4, 2016, 8:45 PM Charles [email protected] wrote:

@DawoudIO https://github.com/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.


You are receiving this because you are subscribed to this thread.

Reply to this email directly or view it on GitHub
#336 (comment)

@gyphon
Copy link

gyphon commented May 20, 2016

May I ask where are we on this?

@rakess70
Copy link
Author

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?

@crossan007
Copy link
Contributor

I guess it would make sense for me to address this in #612.

By that token - any UI input you have would be appreciated.

@rakess70
Copy link
Author

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.

@DawoudIO DawoudIO modified the milestone: 2.1.0 Jun 3, 2016
@crossan007 crossan007 added this to the 2.3.0 milestone Sep 7, 2016
@crossan007 crossan007 self-assigned this Sep 7, 2016
@DawoudIO DawoudIO modified the milestones: 2.3.0, 2.4.0 Oct 23, 2016
@crossan007 crossan007 modified the milestones: 2.4.0, 2.5.0 Nov 23, 2016
@VictorPitta
Copy link

Are there any updates on this? This is the only thing stopping me from using this product

@bosundare
Copy link

Any update on this issue? Want to implement this platform, but I am unable to do so without this feature enabled for my org.

@MrClever
Copy link
Collaborator

MrClever commented May 12, 2020

@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 👍

@bosundare
Copy link

@MrClever Thanks for getting back. Already watching it, and hopefully this feature would be available soon.

@DawoudIO DawoudIO removed this from the Backlog milestone Mar 21, 2021
@rockson-waters
Copy link

@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 👍

Thanks

@xtremelora
Copy link

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.

@MrClever
Copy link
Collaborator

MrClever commented Jan 3, 2022

Here I am again and I see that this has not been resolved yet, too bad, is a great software.

@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 🙂

@VictorPitta
Copy link

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!

@DawoudIO
Copy link
Contributor

DawoudIO commented Mar 4, 2023

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.

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Jun 23, 2024
@VictorPitta
Copy link

VictorPitta commented Jun 23, 2024 via email

@respencer respencer removed the Stale label Jun 23, 2024
Copy link
Contributor

github-actions bot commented Aug 6, 2024

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.

@github-actions github-actions bot added the Stale label Aug 6, 2024
@VictorPitta
Copy link

VictorPitta commented Aug 6, 2024 via email

@github-actions github-actions bot removed the Stale label Sep 9, 2024
Copy link
Contributor

github-actions bot commented Oct 9, 2024

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.

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests