You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'll describe the use case as I'm interested in better ways of solving this problem than the first one we have in mind!
We use Jira for managing development projects and we've been using Jira Work Management for managing client work, marketing deliverables, and other projects.
We'd like to have a 'shipping' or 'order management' board that can be reviewed by relevant members of the team, for tracking production, fulfillment, through to product delivered. Our wish is to also associate these with the relevant client project. So we figure we'd create an issue in the "AcmeCo" client project, e.g., "Ship 5 widgets," which would get the label "shipping." This can then be turned into a board by filtering by the label "shipping," and then creating a board from that filter.
Feels a bit clunky and like there is perhaps a better way of going about this. Any ideas?
Hi @Evan
A central Board is a good idea - with filtering assigned, which can bring issues in based on metadata (like labels) - this is a nice, simple method to visualise multiple data sources in one place.
I'd also consider if a dashboard is a good option. You could have multiple gadgets displaying filtered results - eg. a Shipping Filter. You could also use more visual gadgets like pie charts or graphs if needed.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.