Fixed fonts

Edit mockup is too simplistic - widget needs fresh mockups to account for different ticketing systems (BZ, pagure, github, etc.)

Also note personal vs project level information. E.g., view a list of project-related tickets on project hubs, view tickets waiting on me (across all projects) on my personal stream. Etc.

Assigning this ticket to myself for mockup updates

Different Tracking Systems

Thoughts around data we might need for each type.

Trac

• URL / what project
• status
• when opened
• when most recent activity
• who opened
• who assigned

Pagure

• URL / what project
• tags to filter (* for show all) white or black list
• status
• when opened
• when most recent activity
• who opened
• who assigned

Bugzilla

• URL
• product
• component
• who assigned
• status
• when opened
• when most recent activity
• who opened
• who assigned

Things About Tickets Individuals Want To Know

• What tickets are waiting on me (any project?)
• What's the status of issues I filed (any project?)

Things About Tickets Projects/Teams Want To Know

• What tickets need attention? (Where's the fire?)
  • What's the most urgent?
  • Who's been waiting the longest time?
• What tickets can I work on?
  • Any tags (eg newbie tagged tickets) for beginners?
• How are we doing overall with our tickets?
• Where's the ticket activity happening right now?

Some ideas for this widget based on above:

Some ideas for this widget based on above:

This looks really nice! I love the 'age' text on the project-based mockups.

A thought: sometimes when I'm reviewing tickets (either looking for low-hanging fruit, or things to close) I'm interested in:

• How long ago was the ticket filed. (Sometimes I'm looking for new ones - they could be easy, or they need a response).
• How long ago was the last comment on the ticket. (Sometimes I'm looking for tickets that have languished and can be closed due to inactivity).
• How many comments are on the ticket? (Tickets with lots of comments roughly correlate to "interest" in the ticket.. so perhaps I should prioritize my work towards those).

These are brilliant, will rethink this one to include these ideas. Not sure if these are different 'modes' for the widget or what. The first two, though, we use as reports on the design team ticket system so i am guessing they are universally useful, the most comments one seems generally useful too!

Here's some more based on Ralph's ideas. These could be templates / modes for the widget you could select from when adding the widget to a page. If you wanted more than one of these, just add another copy of the widget. Could also 'collapse' them into a tabbed widget. (I'm hesitant on that idea, tho, I think the UI would be kind of clunky.)

Here's some more based on Ralph's ideas. These could be templates / modes for the widget you could select from when adding the widget to a page. If you wanted more than one of these, just add another copy of the widget. Could also 'collapse' them into a tabbed widget. (I'm hesitant on that idea, tho, I think the UI would be kind of clunky.)

Okay, here's an example config panel for personal and one for the project hubs. The main diff is that the personal and project hub ticket widgets have different templates (all mocked up above.) Also, the personal asks for the email address of the person in question; the project one just asks for the component name.

Okay, here's an example config panel for personal and one for the project hubs. The main diff is that the personal and project hub ticket widgets have different templates (all mocked up above.) Also, the personal asks for the email address of the person in question; the project one just asks for the component name.

@duffy thanks for the designs, they look really good.

One thing though, I think we'll be using different template for editing a widget vs adding it.
For editing the code has been merged in #138 it has a simple panel with just the fields a widget can be configured with. This panel will also have the 'Delete this widget' button (cf PR #139 which bring the feature to remove a widget from a hub).

Your designs here seem more like what we want when adding a widget to a hub, correct? If so, then they will probably not have this Delete this widget button since when we're adding it, it's not in the hub already :)

How does that sound?

@pingou makes sense! just to sum up our convo in IRC - these edit mockups would require custom templates, which i think are really important to have, but for our first cut to get this out the door we do not need them. the add and edit being the same except for the delete button makes sense too. for future reference, also, here's the summary of how to add widgets:

https://lists.fedoraproject.org/archives/list/hubs-devel@lists.fedoraproject.org/thread/JJXAHYXVB4ZK273R6OQA4IQ5V5NYTHU7/