Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/andrewl/trello-mup
Trello - Mindmup integration tool
https://github.com/andrewl/trello-mup
Last synced: about 1 month ago
JSON representation
Trello - Mindmup integration tool
- Host: GitHub
- URL: https://github.com/andrewl/trello-mup
- Owner: andrewl
- Created: 2014-10-22T16:09:14.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2015-10-22T17:01:26.000Z (about 9 years ago)
- Last Synced: 2024-08-05T22:37:07.078Z (5 months ago)
- Language: JavaScript
- Size: 184 KB
- Stars: 4
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
trello-mup
=========Integrates Trello and MindMup. When run it will do two things:
Add a MindMup node to the backlog list on Trello.
-------------------------------------------------
- create a 4th level node
- add a node attachment just containing the word 'backlog'
- running Trello-mup against the MindMup file will create a new node in Trello and replace the node attachment with the url of the card in Trello.Colour MindMup node according to their status on the Trello board
-----------------------------------------------------------------
- if a 4th level node has a node attachment that corresponds to a URL of a trello card, then the background colour of that node will be set to reflect to the status of the card as it progresses across the Trello board. Broadly speaking 'red' is in progress, 'yellow' is being tested, 'green' is done.Why 4th level nodes? We assume that the hierarchy in the MindMup nodes follows this pattern:
- Goal (Why)
-- Actor (Who)
--- Impact (How)
---- Option (What)@todo
-----
This is a very hacky implementation and needs cleaning up. Notably the MindMup functions should probably live in their own module. Also, because of the requirement to make multiple, by nature asynchronous, calls to the Trello API, the q promise library was used, which led to some hacky refactoring, and probably not entirely correct, changes to variable scopes to ensure their availability during the lifetime of each promise.