Problem Definition

JIRA has setup with components. Each component represent components in the enterprise systems. When issue (story/task) is created first in JIRA first, during the initial analysis phase the component is assigned to the issue in JIRA.
Later during the planning phase, where PMO is creating a plan through Portfolio issues are imported on the portfolio plan. In the portfolio teams and skill sets are defined so that portfolio can suggest resource allocation. The component field is also visible on portfolio now. But currently there is no direct association between component and either team or skill sets. So when portfolio suggests resource allocation (or when PMO 'calculates' for the schedule) the resources picked up are from random teams - without any consideration on the skill set/teams. So the development tasks/stories will get QA or BA resource getting assigned. The only option is to go individually on all the issues and change the resource allocation manually. When there are 100 - 200 different epics (with average 5-10 tasks/stories under each epic) under development for different releases, it becomes extremely tedious job.

Suggested Solution

I think we can have feature/option to link JIRA component with Portfolio skill set or project teams.
One can associate/link component with teams created in portfolio.
For example:
Component "Pricing engine" can be mapped to "Pricing team". Similarly component "XYZ adapter" can be mapped to "XYZ adapter team".

For someone skills are more helpful to plan. In that case one can associate component with skills and this can be many to many relationship.
For example:
Component "Pricing engine" can have multiple skill set associated with it. Other component "XYZ adapter" may have other skill sets, but can share some skill set from "Pricing engine" component.

One can create this association while creating a plan from JIRA issues or from the "Configure" plan option.

Once the link between component and teams/skills is established, portfolio can use it while suggesting resource allocation on a schedule or calculating capacity. Portfolio can now suggests resources which are at least meaningful (based on the teams/skill set).

Again, this link can be kept optional. so only those who require to use can use. Those who do not need it can continue with current behavior.