You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
I think the approach taken by this plugin is not ideal. Providing an input form inside Sentry and using Conduit to create the task means that
the user creating Phabricator task will be some kind of system user, not the person who looked at Sentry and decided to open a ticket. That is usually a bad thing (no email notifications etc. unless creator subscribes manually).
no way to add data other than description and title.
no previews if the user wants to add something to the description
if the user wants to share the task link, they need to find the task manually
Providing such a link would be a much more natural and convenient workflow and it would also be easy to add additional per-project parameters (such as the corresponding Phabricator project, or a default assignee) - just add a configuration option which gets appended to the URL.
There are some cases in which using Conduit has its benefits (e.g. when the Sentry instance is more widely accessible than the Phabricator instance) but IMO those are fairly nontypical.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think the approach taken by this plugin is not ideal. Providing an input form inside Sentry and using Conduit to create the task means that
Phabricator allows preloading most fields in the task creation form via URL parameters, e.g.
https://secure.phabricator.com/maniphest/task/create/?title=new%20error%20from%20Sentry&description=[insert%20stack%20trace%20here]&projects=maniphest&assign=tgr
Providing such a link would be a much more natural and convenient workflow and it would also be easy to add additional per-project parameters (such as the corresponding Phabricator project, or a default assignee) - just add a configuration option which gets appended to the URL.
There are some cases in which using Conduit has its benefits (e.g. when the Sentry instance is more widely accessible than the Phabricator instance) but IMO those are fairly nontypical.
The text was updated successfully, but these errors were encountered: