Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Flume >> mail # dev >> How JIRA Issues are Classified


Copy link to this message
-
How JIRA Issues are Classified
Hello Everyone,

I have ran into JIRA issues like
https://issues.apache.org/jira/browse/FLUME-1621 where very important
features within Flume are not documented properly or not documented at all
and we need to address the problem.

In this particular instance, I think the issue should have been classified
as Improvement or Documentation rather than as a Bug.

Should these be classified as Bugs, Improvements or Documentation.

So my question now is:

In general, when do we classify the JIRA issues as:

- Improvement
- Documentation
- Bug
- Wish
- Task
- New Feature

Are there any guidelines that could help in classifying the issues properly?
+
Mike Percy 2013-03-27, 01:05
+
Israel Ekpo 2013-03-27, 04:47
+
Mike Percy 2013-03-27, 05:25
+
Mike Percy 2013-03-27, 05:28
+
Israel Ekpo 2013-03-27, 06:02
+
Mike Percy 2013-03-27, 06:10
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB