qgil wrote on 2014-05-01 14:31:18 (UTC)
If we have a Phabricator instance one day, would we need to migrate the Trello data we have, or would it be enough to close past/ongoing sprints and start the new ones in Phabricator?
qgil wrote on 2014-05-06 00:52:42 (UTC)
Honestly I think we can do this by hand.
Alright, let's assume that this is the opinion from the rest of Trello users. Otherwise please reopen this task.
spage wrote on 2014-05-22 22:20:59 (UTC)
I reopened this because people can usefully work on this, but it shouldn't block any deployment.
Looking around, it seems you can
- create tasks in response to e-mails to e.g. firstname.lastname@example.org
- call the Conduit API from a script to create tasks, e.g. http://fab.wmflabs.org/conduit/method/maniphest.createtask/
The latter could be e.g. a Trellaphab script that repeatedly calls curl, or something...
- Can flimport and/or the scripts to migrate Bugzilla and RT be recycled in
some way, or do you have another starting point?
- Many Trello tasks are in fact cloned Bugzilla reports. I have no idea how
many, which percentage. Is it possible to prevent an excess of duplicates
- These imports would occur project by project, manually by the respective
Trello owners, without needing to switch off Phabricator.
It is also clear that these migrations would only happen after the Bugzilla
@Qgil yes, project managers and scrum masters will have to spend time doing this. I suspect the first person who needs to migrate a lot of Trello cards (that aren't just bugzilla bugs duplicated in Trello) and who has some technical chops will hack something together, and others will improve it. Like how bingle evolved.
You're all busy, I don't expect any support except answer some e-mails and maybe some basic guidance. :-)
If some of my time is officially allocated, that could allow me to contribute to this effort more promptly (if I worked on it ad hoc, it would take longer, if I found time to work on it at all).