I would definitely see this pairing well with the user feedback entities created by the suggested self-service action from Port's implementation guide: https://docs.getport.io/guides/implementation-guide/launch/#enable-user-feedback

This could enable some back and forth on issues that customers raise rather than having to open a ticket in another platform and follow-up there and then go back in Port to change the status of the request. Discussions would also help provide context to issues/feedback

This would be a good opportunity to allow users to opt-in to applying artificial intelligence based on previous discussions to propose resolution to the discussions that will take place on entities. In the AppSec use case, for example, historical false positive, remediation, or mitigation discussions might be beneficial when a developer initiates an exception flow.

Would this conversation be portal-based data, or a view of something sourced elsewhere?

My initial reaction is to be a bit nervous, so I tried to make this into a more concrete example. Imagine a conversation occurring in the portal around a new component being proposed for a Github-based repository (versus as an issue or pull request feedback within that repo in Github). Having that discussion solely in the portal feels like it could potentially lose context and/or duplicate conversation going on in the source system (or in a work/bug tracking system if your code repository system of choice does not support that conversation in the same way that Github does).

Sharing early wireframe, happy to get your feedback