Open JRJurman opened 8 years ago
Actually determining when a ticket is "good enough" to print could be challenging. I'm open to suggestions here.
@JRJurman Gonna play around with the Trello API and see what's available and then give some suggestions on criterion to print a ticket.
@JRJurman Right now I have a PR that triggers when a new item is added to a list id that is tracked by the watcher. I was thinking of basing a ticket print when a new task is assigned, or moved into a specific list on a board that could be specified by whoever is instantiating the watcher. Thoughts?
I think on ticket assign is going to be our best bet, the only issue is then keeping track of which tickets have already been printed. I'm running into the same issue with the github watch, and I think the best way to go about it might be using a print cache, to check against...
Conversely, I might scrap this design for something a little more straight-forward: #20
Watch to get tickets for a trello user or a board.
This watch should only create tickets once a description has been filled in for a ticket. It should not just be the activity feed. Images and other artifacts outside of text should be ignored.