Why does portfolio require skills even if the allocation for that issue is zero?

[Thomas Fraser]

And is there a better way around this than giving teams that skill even if they don't have it or need it?

E.g.:

Even though there is no allocation for the above 2 skills, Portfolio won't let me allocate this to a team / individual unless they have that skill, which means I have to give this skill to people even if they don't have or need that skill - which seams to defeat the purpose.

On a related note, portfolio doesn't seem to display tasks that can't be scheduled - is there a way of finding these? Otherwise it's easy to lose them and not realise there are unscheduled tasks.

I've tried to raise this as a bug here but it says I don't have permission https://jira.atlassian.com/projects/JPOCLOUD/issues/JPOCLOUD-409?filter=allopenissues

and when I try to follow the link 

I get this:

[Thomas Fraser · Accepted solution]

The answer is that I had only been looking at the 'original estimate' fields, but portfolio also looks at the other 'estimate field' they both need updating to reflect the balance of effort required for each skill.

[Thomas Fraser · Accepted solution]

I found the answer to part of my question - it made the issue fall outside of the schedule window, which also removed it from the scope. To show issues with errors I needed to change the 'Schedule Range' to 'Full'. 

[Thomas Fraser]

So the remaining question is - why won't Portfolio schedule an issue to an individual / team that doesn't have a skill, even though the estimate for that skill on that issue is zero?