Create a dashboard, and add some gadgets is the short answer.
I would start with a filter that returns a list of all the issues that you're interested in ("project in (x, y, z)" for example), save it and then use it on the dashboard in
Hi Ralf, yes, a data view is perhaps one of the most popular dashboards I make and get requests for. Simply it is a dashboard the gives the most information. I open as many columns as I can, like: key, summary, priority, reporter, assignee, components, labels, etc. Almost any usable bit of information. Know most things is JIRA evolve with the user. After a few weeks, I ask or offer, is there anything you want to add or remove, I give options. Then on each column you can sort in alphabetical order, so you can show all the issues that "John" is the reporter, or how many issues involve the "label" "Fast Cars". etc.
so when you start your filter that you want to use for your dashboard, just incorporate as much info options as you want.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs