Importing partners should have the same fields as adding a partner

Summary

Add columns to the partner import to match partner add

Why

Streamlining partner onboarding -- if the info can be imported, banks won't have to go into every partner separately.

Details

Currently partner import has the name and email only

Partner Add has more

Default storage location
Group
Do you want this partner to receive emails for distributions....
Quota
Notes
Documents

Let's leave off documents for this iteration, but add the rest to the import.

Critera for completion

behaviour as described
tests to support the behaviour

Hi, I'd like to work on this, please.

Please do!

@cielf

Hi @cielf, quick question. Do you have a preference for the order of the headers in the csv files to import partners? (I'm planning on creating a new example csv file that will include the additional fields, which is why I ask.) Would you like it to match the order of the fields in the issue, or the order of the fields shown below in the partner model's Schema Information?

# == Schema Information
#
# Table name: partners
#
#  id                          :integer          not null, primary key
#  email                       :string
#  name                        :string
#  notes                       :text
#  quota                       :integer
#  send_reminders              :boolean          default(FALSE), not null
#  status                      :integer          default("uninvited")
#  created_at                  :datetime         not null
#  updated_at                  :datetime         not null
#  default_storage_location_id :bigint
#  organization_id             :integer
#  partner_group_id            :bigint
#

(I know I'm not adding all of the above to the import functionality, I just copied and pasted the schema information to provide a reference in this thread.)

Thanks!

@McEileen

@McEileen -- My initial take is that the best way, consistency-of-experience-wise, would be to have them in the same order as in the "add partner" screen. Does that make sense to you?

@cielf

@cielf Yes, that makes sense. Thanks.

Let's leave group off as well.

The default storage location should be the name of the default storage location.

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

Hello, it looks like this has been marked inactive and stale. I would like to work on this please!

Sorry for the delay - it's yours!

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

Automatically unassigned after 7 days of inactivity.

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

Automatically unassigned after 7 days of inactivity.

Navigation Menu

Repository navigation

Importing partners should have the same fields as adding a partner #5056

Summary

Why

Details

Critera for completion

26 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Importing partners should have the same fields as adding a partner #5056

Description

Summary

Why

Details

Critera for completion

Activity

McEileen commented on Mar 9, 2025

cielf commented on Mar 10, 2025

McEileen commented on Mar 15, 2025

cielf commented on Mar 15, 2025

McEileen commented on Mar 16, 2025

cielf commented on Mar 23, 2025

cielf commented on Mar 23, 2025

github-actions commented on Apr 23, 2025

26 remaining items

ParsannaK commented on Nov 13, 2025

dorner commented on Nov 29, 2025

github-actions commented on Dec 31, 2025

github-actions commented on Jan 8, 2026

github-actions commented on Feb 25, 2026

github-actions commented on Mar 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions