| Summary: | [pmi] Move to separate table upcoming project releases. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Dawid Pakula <zulus> | ||||
| Component: | Project Management & Portal | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | edouard, wayne.beaton | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dawid Pakula
That table will be short for most projects. Does it make sense to maybe just make them stand out, or maybe annotate them with a "new!" logo (or something similar)? (In reply to Wayne Beaton from comment #1) > That table will be short for most projects. > > Does it make sense to maybe just make them stand out, or maybe annotate them > with a "new!" logo (or something similar)? I personally hate "new!" icons ;) But anything that highlight current/latest version will be better than current state. User doesn't want to compare date in head ;) Created attachment 251029 [details]
New Release Badge
The criteria for the 'New!' badge is simply the first release after the current date. Is this what you mean?
(In reply to Edouard Poitras from comment #3) > Created attachment 251029 [details] > New Release Badge > > The criteria for the 'New!' badge is simply the first release after the > current date. Is this what you mean? I like it. (In reply to Wayne Beaton from comment #4) > (In reply to Edouard Poitras from comment #3) > > Created attachment 251029 [details] > > New Release Badge > > > > The criteria for the 'New!' badge is simply the first release after the > > current date. Is this what you mean? > > I like it. Me too. (In reply to Dawid Pakula from comment #5) > Me too. Ship it. Done! |