Wishlist: Prefixing cards with the Sentry project name.

[PiDelport]

This should probably be configurable: it would be highly useful if you have multiple projects posting to the same Trello board/list, but not so much if you only have a single project, or use per-project boards/lists.

[DamianZaremba]

I think both the card title and description should be configurable, probably something like; Title: %project_name%: [%error_level%] %error_message%

Description: %error_traceback%

%error_link%

As an input and textarea boxes on the config form defaulting to something like the current setup. I need to finish converting the plugin over to use the oauth setup (properly) which I started the work for last month, first.

[PiDelport]

As mentioned in #3, if cards are going to be updated when events retrigger, it's worth worth thinking about support for more dynamic fields like the trigger count, too.

For the actual template syntax, wouldn't Django-style template syntax be a better option?

[DamianZaremba]

Probably an inline Django template to save re-inventing the wheel, the above was more thoughts on defaults :)

Trigger count is available as data from Sentry so wouldn't need to be calculated, I'm not sure how plugin interaction is going to work for triggers on existing events.

You could end up with a case where by you get 10k of triggers on an event, Sentry will happily group those and update the database - if we trigger on each we're now hitting the api 10k times, which impacts the network stack and response time of being able to stash triggers.

I did propose an idea of using a queue system which in this case could be used to rate limit and trigger plugins in a non-blocking fashion. Though you'd still have an issue of backing the queue up.

An alternative might be to look at the buffer code and deal with grouped updates so you only get 1 updated per which might be x thousand updates.... I'll have to have a poke and see what the best way of updating is.

Changing to support custom templates shouldn't be too hard.