Teambox Mantis Bridge - synchronizes tasks
These are some screenshots of what it looks like using the Teambox-Bugtracker-Bridge to synchronize tasks.
In the screenshots below:
We have four task lists:
Original state of Teambox and MantisThe task in the none-tracked task list "Needs to be investigate" should be completly ignored, since we have only added the task list ids of "High priority bugs" and "Low priority bugs" to the configuration file.
There is an existing task in Mantisbt that also should be ignored since it is not in any of the monitored lists in Teambox.
First execution of the bridge, syncs all tasks from Teambox to MantisNote that the bridge has added (mt:XXX) where XXX is the mantis bug number to the title of the Teambox tasks
Viewing a single bug, note that it has added teambox id as description, and teambox id for each synced note from Teambox.
The hash is used to determine if a note has been modified since last sync.
Adding a comment in Mantis to one of the tasks that were transferredAdding the comment:
After executing the bridge:
Adding another comment in Teambox as a reply to the comment from Mantis, and executing the bridge will transfer the comment over to Mantisbt:
Editing an old note / commentThe mantis developer realizes his mistake and edits his old comment
Synchronize it over to Teambox:
The Teambox user also edits an old comment (note that you should have set in the Teambox preferences that notes should be able to edit even after the 15 minute limit)
... and after the bridge execution, the edited note is transferred from Teambox to Mantis:
Solving a task in MantisbtThe developer has made significant progress and actually solved the problem, and update the Mantis bug accordingly:
when executing the bridge, the task is automatically transferred to the the "Resolved Bugs" task list in Teambox, note that it has added (mt:resolved) marker.
Re-opening a solved task in TeamboxUnfortunately, the problem was not properly solved, the Teambox user moves it back to the bug list in Teambox and adds his comment:
and after execution the task has now changed status from "resolved" to "new":
See the github page for detailed information.