Discussions & Comments on entities
exploring
S
Simon Beaulieu
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
Aidan O'Connor
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.
R
Richard Rein Jr
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).
R
Richard Rein Jr
Revisiting my original comment based on some additional context now (an additional 10+ months using the product, and 8+ months of our uses using what we have built in it)...
We absolutely have use cases where having some discussion/being able to comment on entities would be useful - but most of the ones that I can identify are where the entities originate/are stored in Port This includes things like the user feedback system that Simon Beaulieu mentions above (because we have included something similar in our Portal), as well as other similar examples (we are currently building out a collection of code samples to provide the next layer behind project templates, and similarly these will only live in Port, and being able to have a threaded conversation/tag people would be incredibly useful).
For entities that really come from integrations elsewhere, I think that I still like the idea of keeping the conversation in one place (and since you can't prevent it from having in the source system - like within the context of a incident tracking system - that one place likely isn't Port...but we can certainly surface that conversation as related data within Port, especially now that we can customize the entity page to our liking) . Where I think that leaves me is I would appreciate the ability to customize this functionality, turning it on or off per blueprint.
Matan Grady
Sharing early wireframe, happy to get your feedback
Gur Shafriri
exploring