Use Trello

[sagotsky]

Integrated support still isn't quite up to snuff yet. Let's throw more APIs at it. Instead of webhooks, labels, and voodoo...

Use Trello to manage the roadmap.

We'll have one intake board with bugs and ideas imported from GetSatisfaction and Engineering from Github:

Nothing on this board is set in stone yet. It's just a collection of the ideas we've received.

We will also have a roadmap board with a backlog list (aka the In the Future milestone) and a list for each planned milestone:

Backlog	Sept 16	Oct 30	Dec 14
etc	etc	etc	etc

This board does indicate what's planned and will be used to generate the roadmap page. The /roadmap page will just be a rendering of what's on these lists. /backlog will be similar, but for the backlog list. The idea is that the roadmap should display items from exactly one easily managed source, instead of patching it together from a variety of sources and allowing a number of events and labels to affect it.

Use Trello events for notifications

All event notifications should trickle down from trello into our other services.

• Ticket creation -
• Scheduling notification (GS and desk will be notified by github events, not by trello events)
• Completion (GS and Desk will be notifyed by GH events)
• Milestone changes. - When a trello card moves in the milestone board, github should be updated.
• User assignment. When a card is assigned to someone, assign it to their GH account. (what do if multiple trello assignees?)

TODO 09/11/13

• Fix labels. They're not applying on osops.
• Get GH status via ajax
• Never include PRs. Only issues.
• Github should only use items tagged with engineering.
• GS topics should include links to GS and GH if both are available.
• GH issues should be excluded if they are mapped. Let the GS topic have both.

TODO 09/12/13

• Make it purty. Dan's labels are sweet.
• New design:
  1. Current mielstone, rendered.
  2. List of links to each upcoming milestone.
  3. Backlog, rendered as three columns.
  4. List of links to past milestones.
  5. Links load table with ajax. Each includes a permalink to just that table.
• Find out why trello missed http://community.openscholar.harvard.edu/openscholar/topics/allow_site_owners_to_redirect_people_profile_pages
• When a GS topic enters a milestone list, if it isn't linked yet create the GH issue and link them.
• GS topics can get their status from linked GH issues
• Pretty urls. urlencode gives us Sept%2016. Replacing spaces with dashes would be nicer.

TODO 09/18/13

• No ajax. Just use regular pages for simplicity's sake.
• All navigation should take place in the select box. No more tabs.
• Legend w/ checkboxes. Show/hide different statuses.
• Double check that labels are being created. (Maybe check on page loads too. If a case is loaded with no label, maybe we can add it retroactively?) (Labels were working fine. What wasn't was Trello on osops. With that out of commission labels couldn't possibly update).

TODO 09/19/13

• Checkboxes should opt in like taxonomies. Clicking done shows only done. Adding in testing shows done and testing. All are off by default, so nothing is shown.
• Checkboxes to bottom
• Span around label text
• Fourth column for hotfixes. Populate from GH.
• Display on an openscholar themed vsite, so @dancabral's 4th column will flex.
• Call it roadmap2. The trello part is a secret.
• Backlog is a separate link (always visible), not part of select.
• Fix select for viewing within a vsite. (This will be appearing on a vsite with a domain, so it's no problem)

TODO 09/20/13

• Releases/Backlog as tabs
• 'select a milestone' -> 'select a release'
• No release archive (for now)
• Order: Features, Bugs, Engineering
• Select and title are redundant. Remove the title and select the current milestone.

Backlog

• No hotfixes
• No status
• First tab is projects

When there's time...

• Filter widget inspired by trello label selector.
  • Filters are off by default (but colored)
  • When all are off, no filtering
• Import tickets from previous milestones. Probably loop over one milestone in each pass. Can they all be engineering, or should we use GS for those where that works. Alternatively, we could use type: feature/bug...
• Add a scrollbar lib? I'm partial to jquery's perfect-scrollbar plugin.

[sagotsky]

It takes a full minute for the getsatisfaction API to get all the tickets. GH is only somewhat better. That's fine for a one time import, but if we're going to be doing this on a regular basis (hi, cron!) it seems suboptimal.

Maybe there's a way to get IDs in a certain range? Or at the very least a date range. Then I can store the id of the newest imported ticket.

GS and GH give me active_since and since. These let me get issues with activity after a certain time.

Only problem is that activity is any update, not just creation. This is a start, since I can query for active after time, and then filter those based on what was also created after that time, but it's not ideal.

Both will let me get items sorted by created date, descending, so I can manually get the most recent that way. Just do one page at a time, filter the created date, and if I haven't filtered out anything yet, get the next page. This is probably the most efficient in terms of api calls, but not in terms of LOC.

[sagotsky]

Working on webhook reactions. When a card moves across lists, I get a before and after on the card, meaning I can see the lists it's moving between. That's not the case with boards. I can see the source and dest board, but I have no idea what list the card is coming from. This is significant because I was hoping to attach a label at this point. Looks like I have to label each card when it's created.

[sagotsky]

Label note. Labels colors are bound to cards. Label titles are bound to boards. When I move an orange card, it keeps orange, but the value of orange may change. Maybe there's a better way to figure out the type of a card.