Hi, It's not instead of it's in addition too. The presence of Epics doesn't prevent the use of labels and you can filter with labels on the agile board it's just really gross. You have to create quick filters or type in JQL. Epics get's you drag and drop as well as some other UI niceness like tracking how close an Epic is to completion.
There is also no process change where we stop using labels and start using Epics. Ariel On Thu, Aug 6, 2015, at 10:04 AM, Jake Luciani wrote: > Is the reason to use epics over labels simply because the agile board > doesn't support it? > > On Wed, Aug 5, 2015 at 12:42 PM, Ariel Weisberg > <ariel.weisb...@datastax.com > > wrote: > > > Hi, > > > > At this stage I wasn't going to propose a process change. My goal is to > > observe and report mall cop style so I can present what happens the way we > > currently operate. Right now Epics are just a way for me to bucket and then > > rank things inside a release based on what they are, enhancement, core to > > the release (Materialized Views, 8099), bugs or failing tests. > > > > Regards, > > Ariel > > > > On Wed, Aug 5, 2015 at 11:43 AM, Gary Dusbabek <gdusba...@gmail.com> > > wrote: > > > > > Who would have the burden of assigning and managing epics? > > > > > > Thanks, > > > > > > Gary. > > > > > > > > > > > > On Tue, Aug 4, 2015 at 3:08 PM, Ariel Weisberg < > > > ariel.weisb...@datastax.com> > > > wrote: > > > > > > > Hi all, > > > > > > > > I am playing with using an Agile board to track what goes into each > > > > Cassandra release. What slips from release to release, as well as what > > is > > > > added after the initial set of tasks for a release is started. > > > > > > > > You can see the SCRUM agile board I created here > > > > < > > > > > > > > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=83&view=planning.nodetail&selectedIssue=CASSANDRA-9908&epics=visible > > > > > > > > > . > > > > > > > > The board has two ways to bucket issues. One is the release in which > > the > > > > issue is supposed to be fixed. The other is Epics. Epics are not > > > associated > > > > with a release so a feature like 8099 might have an epic. Epics can be > > > used > > > > to bucket issues within a release or across releases. > > > > > > > > I would characterize Epics as being a lot like labels that integrate > > with > > > > the Agile board. You can use labels with Agile boards by adding quick > > > > filters to select on labels. > > > > > > > > The current set of issues types associated with the C* project in ASF > > > JIRA > > > > doesn't include Epic or Story. I don't use Story, but Epic would be > > > useful > > > > for further categorizing things. > > > > > > > > When I asked ASF Infra about it they said that this needs discussion > > and > > > > approval by the PMC. > > > > > > > > Thanks, > > > > Ariel > > > > > > > > > > > > > -- > http://twitter.com/tjake
