The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Although sampler and views_sparkline are pretty close for D7 (if not already there) (As of 2012-11-04, sampler has a stable release and views_sparkline hasn't been started yet), the actual metrics in project_issue will need to be ported to D7. Basically, where all the data is coming from is different now. I think it's mostly just the classes in the project_issue/metrics directory that'll need to be touched -- the .inc files are probably all fine as-is.
This would be necessary if we want to keep displaying the sparklines in the "issues for X" block on project pages.
Comments
Comment #1
redhatmatt commentedestimate 8hr, talked to dww.
Comment #2
senpai commentedThe views_sparkline D7 version has not been started. It does not even have a D7 branch yet.
Comment #2.0
senpai commentedviews_sparkline
Comment #2.1
senpai commentedAs of 2012-11-04) sampler has a stable release and views_sparkline hasn't been started yet
Comment #3
dwwThis isn't about display and doesn't touch views_sparkline at all. This is about the backend plugins to compute the data via Sampler API, and there's already a 7.x-1.0 of that. I don't care if we don't display this data the day we launch, but it'd kinda suck to not at least keep the data collection going. Otherwise, we just create a mess for ourselves with holes in the data we need to fill later, and that will take (much)? longer to get right.
Comment #4
drummtag
Comment #5
bdragon commentedMine.
Comment #6
bdragon commentedThis should be fixed now.
I had to do more extensive work on project_issue_opened_vs_closed_by_category than on the others, but all three should be looked at later for comparison to ensure the numbers make sense.
http://drupalcode.org/project/project_issue.git/commit/a50eaaaa5a0e3e28a...
Comment #7
dwwCool, thanks! No time to look at the diff. Should we open an issue somewhere about QAing this?
Comment #8.0
(not verified) commentedtypo