In T3179#162681, @dolftax wrote:

In T3179#111010, @anda wrote:

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.

We probably have around 1500 issues to migrate, with a few different jira project names /labels. Of guess that this would best be translated to a label in phabricator.

Did you find a JIRA -> Phabricator migration script?

In T3179#111010, @anda wrote:

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.

We probably have around 1500 issues to migrate, with a few different jira project names /labels. Of guess that this would best be translated to a label in phabricator.

I'd love to have Redmine importer as well.

srry :(

Are there steps to reproduce this?

As I recall, yes. But the only install I'm aware of that uses it (Asana itself) also disables the mail prefix, and might disable subject variance, although I'm not sure.

in Asana, does the title updates the ticket's title?

It makes more sense to use the mail message title in Asana, as the integration is essentially replacing mail. It makes less sense to use it in JIRA, and the object's handle's full name is probably the right string to use. I think it's probably OK to just use that universally.

You can remove the prefix with metamta.differential.subject-prefix, and remove the action with metamta.vary-subjects, but both of these will also affect mail.

Got it - those are fair points. We'll maintain a fork of Phabricator with this Asana integration, so please ping me if you'd like to reference it at some point in the future!

To set expectations, this is a very low priority for the upstream. Most prior Asana/JIRA work in this vein has been for paying customers (see Prioritization).

Facebook has this exact kind of integration with their internal tasks tool - it's extremely useful for communicating the engineering progress of a task to non-technical team members, and it builds an explicit relationship between tasks and diffs, which very often go hand in hand. Maniphest and JIRA both already have this type of integration with Differential - it would be great to have the same thing for Asana.

The existing Asana integration is for creating an Asana when you create a Differential review for the purpose of reviewing the Differential.

Are you using the current integration?

In T5422#146501, @pgiles wrote:

We're trying to integrate with JIRA 7.1. Is JIRA 7 or 7.1 supported?

We're trying to integrate with JIRA 7.1. Is JIRA 7 or 7.1 supported?

Trac wiki import to Phabricator's Phriction.

Yet another set of scripts ...

I wrote a simple github to phabricator import script if anyone is interested : https://github.com/kakaroto/github_to_phabricator

AFAIK, DoorKeeper is a way to represent foreign objects and to interact with them; Here the remote object-like thing would be the chat channel?
This might be better served by:

• Fixing/improving chat-bot, or
• Use hipchat's write-only api with the feed.http-hooks (Might require extra steps), or
• A feed worker, like DoorkeeperFeedWorker, sans the Doorkeeper part.

I know you don't provide support for writing third party extensions, but is it possible to do what I am trying to do with Doorkeeper currently? Basically I guess I need to define conditions which define what is published and where it is published to.

I'm mostly just curious in learning about real integration use cases.

To chime in on the hijacked direction of this thread. I had my users switch from XMPP/pidgin to conpherence for a week to see how viable it was. Here were the main complaints. My comments are added at the end of some in italics.

Personally, I'd much rather use Conpherence because I absolutely love mentions and find them very useful. Having said that, convincing 200+ others to use Conpherence is much more difficult.

(Yes, Doorkeeper is send stuff out, Nuance is pull stuff in).

What do you need from HipChat that you'd want to see in Conpherence? We've been debating the usefulness of features like Feed inside the Conpherence, curious if you'd use it and what you'd want to see.

Fogbugz to Phabricator import script: P1795

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.

In T3179#81309, @cburroughs wrote:

some examples from what we did might help. I'd only go down that path if you have significant expertise in the source system and phabricator

Artifacts at: D10754 P1403 P1404 P1405 P1406 P1407

For installs with phabricator.developer-mode disabled, we could conceivably fail tasks with a missing class permanently, although I'm hesitant about that (it's possible that they're important and the administrator just uninstalled an extension by accident).

Depends entirely what "Other Tools" means. Conduit and Doorkeeper will be built in means of talking to external systems. Remarkup can certainly be expanding to offer more flexibility in writing content into Phabricator. Custom Fields and Event Listeners also allow for customization. Forking and maintaining patches are also what we recommend to people who need heavy integration/customization.

We never implemented this locally.

@hach-que, were you able to move forward with implementation of what you've proposed?

In T3179#83850, @mattflaschen wrote:

In T3179#81309, @cburroughs wrote:

Building on the work from the Blender team (thanks!) we have been able to plan a migration of ~40,000 trac/trello tickets into phabricator.

Thanks!

Can you add license/copyright information for the pastes?

If we are going to use Phabricator more extensively at our place, we will need to migrate cases and projects from FogBugz, eventually.

In T3179#81309, @cburroughs wrote:

Building on the work from the Blender team (thanks!) we have been able to plan a migration of ~40,000 trac/trello tickets into phabricator.

Doorkeeper is more infrastructure than a real application. See also T3906. None of this is extensible right now.

T5462 also has some additional hints on integration with external trackers.

That is, I think JIRA and Asana connectors use some portions of it, but it's not for public use.

It doesn't exist in any usable form.

I don't see a little prototype bomb next to Doorkeeper but there is no /doorkeeper to do anything with and it's not on phabricator.org. Is it something that people should use today?

Generically, this is our Doorkeeper product. In the meantime you can use Custom Fields to track external URLs if needed.

Thank you @cburroughs! Maybe a wikimedian will contact you soon, since we also need to deal with a Trello to Phabricator migration.

To contribute to this, some months ago we moved from a LiquidPlanner instance with a few thousand tasks to PH. From what I remember now, if conduit was a bit more powerful it would be a lot easier to do such things (it's almost like if PH don't want people to migrate from other systems into PH). The basic things missing from conduit, last time I looked at it, was the ability to specify dates other than the current one for any action you do (e.g. task creation date, comment date).

Building on the work from the Blender team (thanks!) we have been able to plan a migration of ~40,000 trac/trello tickets into phabricator. Summary: (A) a lot of work (B) gross code (C) basically working (huzzah!). If you are considering doing something similar some examples from what we did might help. I'd only go down that path if you have significant expertise in the source system and phabricator (as in if you break your phabricator install you will need to fix it on your own).

Closed by commit rP7d9eb8baaf86.