Issue Summary

In Jira Align, the Import process allows Capabilities to be created without assigning an Owner, even when the Owner field is mandatory under the Details Panel Settings. If the user performing the import is not a member of the Portfolio, the Capability is created without an Owner. Attempting to update such Capabilities via API Calls results in an error due to the missing Owner field.

Steps to Reproduce

1. Set Owner Field as Mandatory for Capabilities under the Details Panel Settings
2. Perform the import process, ensuring the Owner column is not set
3. Use Jira Align Swagger or any other API client (for example, Postman or Curl) to make a PATCH on a Capability with no owner

Expected Results

• When the Owner field is set as mandatory, the Import process should enforce this requirement and prevent the creation of Capabilities without an Owner.
• Capabilities created without an Owner should be updated via API Calls without encountering validation errors.

Actual Results

• Capabilities are created without an Owner if the import is performed by a user not a Portfolio member.
• API updates on these Capabilities fail with the error:

  Cannot update capability with id XXX. Following properties: 'ownerId' are required.
  

• Capabilities created via the UI or API can't be created without an Owner, ensuring consistency.

Workaround

• Manually assign an Owner to the Capability using the Jira Align UI before attempting API updates.
• Ensure the importing user is a member of the Portfolio to assign themselves as the Owner automatically.