Make Organizations available as a standard field on idea portals so portal users and internal teams can associate feedback with the correct customer/account directly. Merged

What is the challenge?

• We need to capture customer/account demand consistently from the start of the feedback process, but Organizations are not available on the idea portal. Today, this creates two major problems:

  • Not everyone across our organization has access to Salesforce, so they cannot reliably add proxy votes on behalf of customers.

  • We need customer/account visibility to carry through from ideas into promoted features and epics for reporting, roadmap planning, Azure DevOps integration, and release notes.

• Because Organizations cannot be used directly, we rely on custom customer fields instead. Those fields must be manually maintained and updated across ideas, features, and epics as customers change over time. This duplicates effort, creates inconsistency across records, and introduces significant risk of user error.

• Our Organization data is already maintained through our Salesforce integration and reflects our active customer list. We want to use that trusted source of truth instead of recreating and manually synchronizing the same data in multiple custom fields.

What is the impact?

• Adding Organizations to idea portals would:

• Reduce manual work and redundant data maintenance

• Decrease user error caused by updating customer fields in multiple places

• Improve consistency between ideas, features, epics, reporting, roadmap views, ADO records, and release notes

• Let teams capture customer demand even when they do not have Salesforce access

• Ensure customer/account associations are based on a centrally maintained, automatically updated source of truth

Describe your idea.

• Add organization as an optional field in ideas portals.

Alternative
If Organizations cannot be exposed on idea portals, an alternative improvement would be to support a shared custom field option set managed centrally at the field level, rather than separately at each work item level, so the same maintained customer list can be reused across ideas, features, and epics without duplicate upkeep.