Yup, I am seeing this in some other Apache projects as well and
usually if being asked to add more information more reporter gladly
comply as requested.
Have to diligently nudge some JIRA filers at the beginning but usually
people see that more description are better and the habit get pick up
by n
I agree as well. FWIW sometimes I've seen this happen due to language barriers,
i.e. contributors whose primary language is not English, but we need more
motivation for each change.
On July 29, 2014 at 5:12:01 PM, Nicholas Chammas (nicholas.cham...@gmail.com)
wrote:
+1 on using JIRA workflows
+1 on using JIRA workflows to manage the backlog, and +9000 on having
decent descriptions for all JIRA issues.
On Tue, Jul 29, 2014 at 7:48 PM, Sean Owen wrote:
> How about using a JIRA status like "Documentation Required" to mean
> "burden's on you to elaborate with a motivation and/or PR". Th
How about using a JIRA status like "Documentation Required" to mean
"burden's on you to elaborate with a motivation and/or PR". This could
both prompt people to do so, and also let one see when a JIRA has been
waiting on the reporter for months, rather than simply never been
looked at, and should t
+1 on this.
On Tue, Jul 29, 2014 at 4:34 PM, Mark Hamstra
wrote:
> Of late, I've been coming across quite a few pull requests and associated
> JIRA issues that contain nothing indicating their purpose beyond a pretty
> minimal description of what the pull request does. On the pull request
> it
Of late, I've been coming across quite a few pull requests and associated
JIRA issues that contain nothing indicating their purpose beyond a pretty
minimal description of what the pull request does. On the pull request
itself, a reference to the corresponding JIRA in the title combined with a
desc
