Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

Using URL parameters instead of Conduit #2

Open
tgr opened this issue Jul 30, 2015 · 0 comments
Open

Using URL parameters instead of Conduit #2

tgr opened this issue Jul 30, 2015 · 0 comments

Comments

@tgr
Copy link

tgr commented Jul 30, 2015

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

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant