avo-hq/avo

Dashboard Ranges to control Card Ranges

Open

#2,071 opened on Nov 30, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Ruby (308 forks)user submission
Back endEnhancementFront endHelp wanted

Repository metrics

Stars
 (1,778 stars)
PR merge metrics
 (Avg merge 1d 6h) (67 merged PRs in 30d)

Description

Feature

Ability to control Card.ranges from Dashboard.ranges. It is common to have multiple cards on a dashboard that will have a range. Often times that range is the same for all card. For example, if I'm looking at various sales/order numbers, I want them all for the same time period ( month, week, quater, year-to-date, etc) . Screenshot really explains it much better

Current workarounds

Just using one big PartialCard, with multiple queries generating a Hash that's being fed to the card for displaying

Screenshots or screen recordings

dashboard

Contributor guide

Research direction
Investigate how Dashboard.ranges and Card.ranges are currently implemented in Avo, then define a mechanism to propagate the dashboard level range to cards.
Tech stack
ruby
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RubyRuby on Rails
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60