Re: Proposal, add Epic to the set of issue types available in ASF Jira for Cassandra

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 trac

Re: Proposal, add Epic to the set of issue types available in ASF Jira for Cassandra

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 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

Re: Proposal, add Epic to the set of issue types available in ASF Jira for Cassandra

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

Re: Proposal, add Epic to the set of issue types available in ASF Jira for Cassandra

Who would have the burden of assigning and managing epics? Thanks, Gary. On Tue, Aug 4, 2015 at 3:08 PM, Ariel Weisberg 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

Proposal, add Epic to the set of issue types available in ASF Jira for Cassandra

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