-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more detail required #12
Comments
Sure, I wanted to expand the bugzilla one. Trello is harder since the metadata you get from the APIs is utter crap. But I'll try to add detail about which columns the cards where moved from / to. Do you really want to see all tweets in detail? That can generate a lot of noise in the report and I think one would want to mostly report the numbers. |
How much do you tweet about work?! :) For me it's like once a month or something ... |
I try to have it as generic as possible, when you have more than 3 tweets, it's not useful to have that in the report imo. |
For me it would still be useful because I would read all the tweet lines generated by rapport, and then manually replace them with a quick summary if there were too many to include all of them. |
Well, you can have a custom flavor by copying the twitter default template to ~/.rapport/templates and play around. |
I've done this for the github plugin, and have vastly revamped it. Original output:
but merely showing counts of issues / pull requests filed, commits pushed, comments made etc. is not much use unless you want to go the "I made 5 more commits than you this week so I must be working harder/better" route which is clearly totally braindead ;) "8 commits to SUSE-Cloud/automation" doesn't really tell anybody anything. New output is much more oriented around the content of the work. This might be too much detail but at least then it's easy to manually condense into a summary of the technical topics:
|
Would be much nicer if it reported the names of the cards, the content of the tweet, and the titles of the bugs.
The text was updated successfully, but these errors were encountered: