Wishlist: Setting the date for newly-posted cards.

[PiDelport]

It would be nice if sentry-trello could automatically set the date field on cards: this allows an instant overview of what cards are fresh or stale, when viewing the the Trello board.

(Potential discussion: Are any sentry-trello users using card dates differently?)

[DamianZaremba]

Set the date when the error is triggered again or on the first only? Currently it doesn't do anything with the date but updating it/moving the card up the list based on trigger count could be interesting.

Not sure if the plugin interface supports doing that at the moment, I'll take another look over it as we're storing the card url so updating it after creation shouldn't be /that/ hard.

Need to tweak the plugin to optionally auto create cards in the new plugin interface, as well as having the option within the sentry interface anyway.

[PiDelport]

Set the date when the error is triggered again or on the first only?

I was thinking about this, and in my use case, having cards update and raise to the top of the list when events triggered again would definitely be useful. This would also be an opportunity for an updated trigger count to display, if that gets included in the card's title / description template.

Controlling the position based on trigger count would be a different approach, but also potentially useful, depending on peoples' workflow. I'm not sure how that would interact with manual sorting, though.

[DamianZaremba]

Aside from the issues mentioned in #3, updating cards would be nice.

I think probably options for the following should be added;

• Auto create cards on new events
• Update cards
• Re-order cards

The first is done by default currently, with the new plugin API it will be optional with links in the Sentry interface to create an 'issue' manually.

In regards to re-ordering I think it would have to be within list only and the workflow something like

1. take top issue from 'new bugs' list
2. move to 'working on' list - at this point it won't be auto re-ordered
3. order as required

There wouldn't really be a way to tell what's been sorted via the API and what's been done by end users to skip over without some painful relying on history.

As for updating the cards, that shouldn't be too hard - sadly it would mean updating all the data as it would be effectively template output and could possible get recourse intensive.

Probably sorting based on trigger count would turn out to be too expensive (you'd have to loop over every card and parse out the data then compare it - well not every, you'd take some algro where by you find a rough range and iterate from there). It could also be pointless as a high trigger count (say caused by some 3rd party outage) might be less important the actively breaking things.

I'll have a look around the plugin interface and try to think up a way of doing this when I land this evening.

[PiDelport]

The first is done by default currently, with the new plugin API it will be optional with links in the Sentry interface to create an 'issue' manually.

This would be pretty nifty! I can see it being useful for things like staging servers, where miscellaneous breakage is expected, but you occasionally want to raise specific failures to be tracked.

As for updating the cards, that shouldn't be too hard - sadly it would mean updating all the data as it would be effectively template output and could possible get recourse intensive.

My gut feel is that the description, at least, shouldn't be updated: too much complication without a particularly compelling use case. The more i think about it, the more i think the title, too, should be treated as write-once: trying to shoe-horn dynamic data into it feels too much like misuse.

Perhaps an entirely different way of approaching dynamic data is better: one that comes to mind is posting updates as comments on the thread, say for every N triggers (where N can be configurable, or follow an exponential scale). This would allow seeing a history of updates over time, as well as put the updates in context with any other discussion happening on the card. It would naturally lend itself to notifying of events such as Sentry issues being marked as resolved, too.

As for ordering, i strongly think that anything complicated should be avoided. Sorting Trello cards is a general problem, and will probably see a general solution, either as a Trello add-on, or as a core feature (see Sorting a list by vote, date, label, alphabetically, etc. on the Trello Development board). The most complicated thing this plugin should attempt is probably just a simple "bump to top/bottom of list" option.

[PiDelport]

one that comes to mind is posting updates as comments on the thread

I lifted this idea to separate ticket: #5