In jira 8.6.1 settings are now in:

• Administration → Applications → Application links

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.

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

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.

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:

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.

We haven't seen more interest in this in several years.

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.

Next steps:

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.

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 :)

See https://secure.phabricator.com/book/phabcontrib/article/contributing_code/

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

In T3179#198521, @michelkaeser wrote:

In T3179#142498, @lfarkas wrote:

Trac wiki import to Phabricator's Phriction.

Based on svemir's anser in https://secure.phabricator.com/Q12 a not to nice not perfect but more then nothing:

https://github.com/lfarkas/phabricator/blob/master/scripts/util/trac_wiki_import.php

@lfarkas the Github link results in a 404. Do you still have a copy of this script? I am in need of a Trac Wiki importer and yours seems the only one available. Or does anyone else have a working script?

Thanks in advance.

Hi folks,

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

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.

In T3179#142498, @lfarkas wrote:

Trac wiki import to Phabricator's Phriction.

Based on svemir's anser in https://secure.phabricator.com/Q12 a not to nice not perfect but more then nothing:

https://github.com/lfarkas/phabricator/blob/master/scripts/util/trac_wiki_import.php

I'm having some issues using the feed.http-hooks with the system I'm interacting with. My endpoint (trac) requires a CSRF token. I assume there aren't plans to add any sort of (even low-level support) for that? That's totally fine, this is kind of an edge case anyway.

@snaik phabricator doesn't currently support this. You can write your own however using PHPExcel. I can't see upstream supporting this as I can't imagine it would take significantly more time to just pull up muliple tabs unless the tickets are of very poor quality.

Hi all, is there a way to import tasks from an excel spreadsheet? Its often way faster to write tasks down in excel (for bug bashes, costing meetings, etc) and later import them into Phabricator.

Hello to all,

In T3179#169180, @Kunda wrote:

Any MantisBT -> Phabricator migration scripts ?

For those moving from MantisBT into Phabricator Maniphest I'm activily building a full import web based tool that will extract just about anything from mantis, allow editing/ touching up, then process the import into a Phab conduit.

In case anyone is interested, we just released a first version of "remaim", a tool for migrating Redmine issues to Maniphest tasks. Pull Requests are very welcome! https://github.com/tentwentyfour/remaim

I think it starts out as a URL, and then replaced on the client-side with the name after some AJAX. Most of the time I don't have time to see the "before" text.

I don't understand why it's a tag. Does the JIRA link look like a URL or an actual name?

css is it's own world of magick.

I'm faking my way through it.

Here's Chrome's Style page for the element:

I'm just surprised to hear something is still overflowing after D16081.

DoorkeeperTagView is also used for DifferentialAsanaRepresentationField, which is probably easier to set up (?).

The value is rendered here: https://secure.phabricator.com/diffusion/P/browse/master/src/applications/differential/customfield/DifferentialJIRAIssuesField.php;70463e8a16d4cbe0c83b23b9328c4a359072c506$53

I'd need to see it to fix it. These are tags?

@PhabTab Prefer this discussion to occur somewhere other than this task. See Support Resources under Community. But I think if you pull up PhabricatorContentSource in Diffusion and look at Commit History, you should find your answer.

In T3179#181813, @PhabTab wrote:

What could be the alternative method for

PhabricatorContentSource::newConsoleSource()

Was there a previous Phabricator version with this method? Which method replaced it?

What could be the alternative method for

PhabricatorContentSource::newConsoleSource()

Was there a previous Phabricator version with this method? Which method replaced it?

Neither phill nor Bitnami are upstream built/supported.

Unfortunately I cant import with phill. I get:

Any MantisBT -> Phabricator migration scripts ?