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

UX/UI FecFile Feedback #2451

Open
exalate-issue-sync bot opened this issue Dec 18, 2024 · 3 comments
Open

UX/UI FecFile Feedback #2451

exalate-issue-sync bot opened this issue Dec 18, 2024 · 3 comments
Assignees
Labels

Comments

@exalate-issue-sync
Copy link

From the email:

Here are some things I would like to see happen in FecFile. Normally, I have small PACS and JFCs in FecFile and the volume is not excessive; however, this election cycle, I have a couple of campaigns and one, in particular, has a bit of WinRed. I don’t use the import spreadsheet, because I manually have to add in the Conduit Memo/Intermediary so I just manually enter the transactions.

 

QA Notes

null

DEV Notes

null

Design

A few things I would like to see are the following:

Ability to import the intermediary using the import spreadsheet. Seems we should be able to add a column to the spreadsheet for the Intermediary ID, amount, and election period and it should pull to the contributing donor.

Ability to track contributions to future elections (currently, I keep an excel spreadsheet of all G2024 donations for my particular Fecfile clients.)

Ability to track excessive donors

See full ticket and images here: FECFILE-1901

@exalate-issue-sync exalate-issue-sync bot changed the title FecFile Feedback UX/UI FecFile Feedback Dec 18, 2024
Copy link
Author

akhorsand commented: [~accountid:712020:6466b08c-50a2-42ee-ad81-cfe79921d3e8] Can we split this out into individual tickets to track the work? In the description, that straightforwardly seems like import functionality, so I would be ok closing out that feedback and referencing the epic for Import/Export. (This also goes towards Design #1). Design #2 will be our All-Transaction page. Design #3 can be a nice-to-have future functionality, since we haven’t built in any dollar caps and contribution limit tracking (in fact, we’d actively avoided it). Happy to talk through this more.

Copy link
Author

Shannon Clark commented: [~accountid:61b0b42cd5986c006a9e1c94] I don’t mind splitting this into tickets to track the work. I’ll need to run this by [~accountid:61b0b42cc510bc006b5c03ed] and [~accountid:5b93ddba73130a2b8c662e23] first because i’m not sure who wrote this and if it’s something that we’re going to be doing in the near future, or how they would like it to be. I’ll be sure to ask.

Copy link
Author

Jonella Culmer commented: Thanks [~accountid:712020:6466b08c-50a2-42ee-ad81-cfe79921d3e8] and [~accountid:61b0b42cd5986c006a9e1c94]. I don’t mind if we split these out, but I’d like to retain the original feedback If it’s simpler just link to this ticket with the original comments so we don’t lose it. Saying “create an all transactions page” in the new ticket is not a replacement for “being able to modify a spreadsheet to change data columns on import.”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant