Interfaces with external systems.
May 21 2020
Feb 24 2020
Jan 14 2020
In jira 8.6.1 settings are now in:
- Administration → Applications → Application links
May 27 2019
I think the modern answer here is "use Webhooks". They may not do everything you want if you're writing a chat bot (notably, they intentionally do not currently provide a human-readable text representation of transactions) but there generally suitable for publishing changes to Phabricator objects into a remote system and will produce a program with generally reasonable behaviors and no weird demons lurking under the surface.
May 20 2019
May 17 2019
May 16 2019
For all who might need to migrate from trac to Phabricator, feel free to borrow from this bare-bone script: https://gitlab.com/simevo/trac2phab
May 3 2019
The answer here is now pretty unambiguously "Use Webhooks". feed.http-hooks is formally deprecated, Herald remains a terrible idea, and anyone brave enough to touch Doorkeeper can probably figure things out for themselves.
Mar 13 2019
See PHI1125. Recent versions of JIRA (JIRA 8?) still work with approximately the same instructions, but you have to fill out a modal dialog with about 7 required fields first, and none of the fields have real values. That is, the configuration instructions for recent JIRA are:
Aug 3 2018
Jun 19 2018
Feb 9 2018
Jan 31 2018
Because of the high degree of complexity there's basically zero chance we'll ever build this without active customer interest, and we have none today. Closing this until interest arises.
We don't have any use cases for this today so I don't plan to pursue it. It's conceptually reasonable, but complex, and there's no customer interest.
Aug 25 2017
We haven't seen more interest in this in several years.
Aug 15 2017
Jul 5 2017
Jun 2 2017
We haven't received more information on this, so we don't know how to reproduce it and can't move forward. Feel free to file a new issue in the future with complete reproduction steps, per above.
May 30 2017
May 29 2017
In case anyone is still looking for a Trac Wiki -> Phabricator Phriction importer, we have an ugly but mainly functional script I pasted here: P2056. Code blocks are not always converted correctly, but for us that script was enough.
May 24 2017
Our behavior here is also legitimately wrong, and we can look at fixing this upsteam once we understand what's actually going wrong. I think if you dig in a bit you'll find a set of reproduction steps that are something like this:
Indeed there are the predicted error messages in the phd log. I will try to explore more and see what is wrong. It is probably related to the issue I reported (T12726), likely some of the fields are incorrectly created by arcanist in the first place.
All that makes a lot of sense, I will try what you suggest and see if that was the source of the evil.
I suspect this will not reproduce for us given the reproduction instructions. The code is structured like this:
Ops, sorry :)
May 23 2017
May 21 2017
Mar 6 2017
I have written a couple of scripts to semi-automatically convert trac ("done") and roundup (WIP) to phabricator. The included patch based on D10754 but extended does quite a good job at faking timestamps even for subtasks and notifications etc, but the whole thing is neither complete nor bullet-proof or even convenient. Good enough for people who don't mind to get their hands dirty: https://github.com/lambdafu/phabricator-test
Dec 29 2016
Dec 5 2016
Nov 29 2016
That's why I said In my fork. This is custom code.
how could you do this?
i cant find this configuration in my phabricator application
Nov 24 2016
Looks like the JIRA's default door keeper worker. I guess it is automatically discovered when you run arc liberate command.
If anyone else is looking for this, we have this extension in our local install P2019, which does custom things to a JIRA ticket based on Revisions.