How can we best use this system to provide a high-level overview for Nodes?

14196
Reporter: ahahn
Assignee: ahahn
Type: Epic
Summary: How can we best use this system to provide a high-level overview for Nodes?
Priority: Major
Status: Open
Created: 2013-10-10 12:04:08.559
Updated: 2013-10-10 12:46:10.463
        
Description: Draft, to be discussed:
- create high-level backlog items as Epics; keep the wording of title and summary so that they can be presented as a concise list to stakeholders for information and prioritization. On writing, assume that this is public and intended for a non-technical audience
- use appropriate labels to allow a filter on those Epics (propose: "backlog" and perhaps a component like "portal"); open question: is there a better way of doing this?
- filter "Backlog" (http://dev.gbif.org/issues/issues/?filter=11706): to be configured accordingly, and shared to make publicly visible
- for up-to-date sorting of the list, supply the fix version information, so that the next upcoming additions can be bubbled to the top, and unscheduled ones end at the bottom
- any related issues should be linked to the Epic for coordinated development, but it should not be expected that the stakeholders have to read those]]>