You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2011/06/04 17:06:49 UTC

JIRA report strategy; how to handle duplicates?

I've been doing some experimentation with the JIRA report.

The following configuration IMO produces a reasonable-looking report [1]:

<onlyCurrentVersion>false</onlyCurrentVersion>
<columnNames>Fix Version,Key,Summary,Type,Resolution,Status</columnNames>
<!-- Sort cols have to be reversed in JIRA 4 -->
<sortColumnNames>Key DESC,Type,Fix Version DESC</sortColumnNames>
<resolutionIds>Fixed</resolutionIds>
<statusIds>Resolved,Closed</statusIds>
<!-- Don't include sub-task -->
<typeIds>Bug,New Feature,Task,Improvement,Wish,Test</typeIds>

As mentioned elsethread, issues should be marked as resolved with the
appropriate fix version when fixed in SVN; and issues should only be
closed after the release has been published.

What is not so clear is how to handle duplicate reports.
If these are to be included in the report, then the Fix versions will
have to be maintained.

If not, then it's important that all duplicates are resolved as
Duplicate rather than Fixed.

Views?

[1] http://people.apache.org/~sebb/NET_3_0_1RC3/jira-report.html
Additionally filtered as follows:
<fixVersionIds>3.0.1,3.0,2.2</fixVersionIds>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: JIRA report strategy; how to handle duplicates?

Posted by Phil Steitz <ph...@gmail.com>.
On 6/4/11 8:06 AM, sebb wrote:
> I've been doing some experimentation with the JIRA report.
>
> The following configuration IMO produces a reasonable-looking report [1]:
>
> <onlyCurrentVersion>false</onlyCurrentVersion>
> <columnNames>Fix Version,Key,Summary,Type,Resolution,Status</columnNames>
> <!-- Sort cols have to be reversed in JIRA 4 -->
> <sortColumnNames>Key DESC,Type,Fix Version DESC</sortColumnNames>
> <resolutionIds>Fixed</resolutionIds>
> <statusIds>Resolved,Closed</statusIds>
> <!-- Don't include sub-task -->
> <typeIds>Bug,New Feature,Task,Improvement,Wish,Test</typeIds>
>
> As mentioned elsethread, issues should be marked as resolved with the
> appropriate fix version when fixed in SVN; and issues should only be
> closed after the release has been published.
>
> What is not so clear is how to handle duplicate reports.
> If these are to be included in the report, then the Fix versions will
> have to be maintained.
>
> If not, then it's important that all duplicates are resolved as
> Duplicate rather than Fixed.

Sounds reasonable to me to either maintain the fix version and
resolve simultaneously as fixed or just CLOSE one as duplicate.  I
can imagine (and I think I may done it) scenarios where the
underlying cause of two issues is the same, so it is correct to mark
one as duplicate; but the issue impacting users appears to be
different, or at least complementary.  In that case, I like to keep
both issues open and resolve them both as fixed when the underlying
problem is fixed in svn, closing both on release with the fix
version of the release.  In cases where the reported problem really
is the same - i.e., there is nothing that one report adds to what
has already been reported, I think CLOSEing one as duplicate is
appropriate.

Phil


> Views?
>
> [1] http://people.apache.org/~sebb/NET_3_0_1RC3/jira-report.html
> Additionally filtered as follows:
> <fixVersionIds>3.0.1,3.0,2.2</fixVersionIds>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: JIRA report strategy; how to handle duplicates?

Posted by sebb <se...@gmail.com>.
On 4 June 2011 16:20, Gary Gregory <ga...@gmail.com> wrote:
> I like the report. Can you put it in [parent]?

I don't thnk that would work in general.

To make it usable, I had to specify the fix versions, because there
are currently a lot of issues without fix versions (some may be
incorrectly resolved duplicates).
And unfortunately the blank versions sort first.

I suggest you try it for yourself and see without the fix versions.

I suspect there will be a lot of work to add the correct fix versions
to every JIRA issue.

> Gary
>
> On Jun 4, 2011, at 11:07, sebb <se...@gmail.com> wrote:
>
>> I've been doing some experimentation with the JIRA report.
>>
>> The following configuration IMO produces a reasonable-looking report [1]:
>>
>> <onlyCurrentVersion>false</onlyCurrentVersion>
>> <columnNames>Fix Version,Key,Summary,Type,Resolution,Status</columnNames>
>> <!-- Sort cols have to be reversed in JIRA 4 -->
>> <sortColumnNames>Key DESC,Type,Fix Version DESC</sortColumnNames>
>> <resolutionIds>Fixed</resolutionIds>
>> <statusIds>Resolved,Closed</statusIds>
>> <!-- Don't include sub-task -->
>> <typeIds>Bug,New Feature,Task,Improvement,Wish,Test</typeIds>
>>
>> As mentioned elsethread, issues should be marked as resolved with the
>> appropriate fix version when fixed in SVN; and issues should only be
>> closed after the release has been published.
>>
>> What is not so clear is how to handle duplicate reports.
>> If these are to be included in the report, then the Fix versions will
>> have to be maintained.
>>
>> If not, then it's important that all duplicates are resolved as
>> Duplicate rather than Fixed.
>>
>> Views?
>>
>> [1] http://people.apache.org/~sebb/NET_3_0_1RC3/jira-report.html
>> Additionally filtered as follows:
>> <fixVersionIds>3.0.1,3.0,2.2</fixVersionIds>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: JIRA report strategy; how to handle duplicates?

Posted by Gary Gregory <ga...@gmail.com>.
I like the report. Can you put it in [parent]?

Gary

On Jun 4, 2011, at 11:07, sebb <se...@gmail.com> wrote:

> I've been doing some experimentation with the JIRA report.
>
> The following configuration IMO produces a reasonable-looking report [1]:
>
> <onlyCurrentVersion>false</onlyCurrentVersion>
> <columnNames>Fix Version,Key,Summary,Type,Resolution,Status</columnNames>
> <!-- Sort cols have to be reversed in JIRA 4 -->
> <sortColumnNames>Key DESC,Type,Fix Version DESC</sortColumnNames>
> <resolutionIds>Fixed</resolutionIds>
> <statusIds>Resolved,Closed</statusIds>
> <!-- Don't include sub-task -->
> <typeIds>Bug,New Feature,Task,Improvement,Wish,Test</typeIds>
>
> As mentioned elsethread, issues should be marked as resolved with the
> appropriate fix version when fixed in SVN; and issues should only be
> closed after the release has been published.
>
> What is not so clear is how to handle duplicate reports.
> If these are to be included in the report, then the Fix versions will
> have to be maintained.
>
> If not, then it's important that all duplicates are resolved as
> Duplicate rather than Fixed.
>
> Views?
>
> [1] http://people.apache.org/~sebb/NET_3_0_1RC3/jira-report.html
> Additionally filtered as follows:
> <fixVersionIds>3.0.1,3.0,2.2</fixVersionIds>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: JIRA report strategy; how to handle duplicates?

Posted by Dennis Lundberg <de...@apache.org>.
On 2011-06-04 17:06, sebb wrote:
> I've been doing some experimentation with the JIRA report.
> 
> The following configuration IMO produces a reasonable-looking report [1]:
> 
> <onlyCurrentVersion>false</onlyCurrentVersion>
> <columnNames>Fix Version,Key,Summary,Type,Resolution,Status</columnNames>
> <!-- Sort cols have to be reversed in JIRA 4 -->
> <sortColumnNames>Key DESC,Type,Fix Version DESC</sortColumnNames>
> <resolutionIds>Fixed</resolutionIds>
> <statusIds>Resolved,Closed</statusIds>
> <!-- Don't include sub-task -->
> <typeIds>Bug,New Feature,Task,Improvement,Wish,Test</typeIds>
> 
> As mentioned elsethread, issues should be marked as resolved with the
> appropriate fix version when fixed in SVN; and issues should only be
> closed after the release has been published.
> 
> What is not so clear is how to handle duplicate reports.
> If these are to be included in the report, then the Fix versions will
> have to be maintained.

IMO duplicates should not be included in the report. If they are
descriptions of the same problem, then they do not add any value in the
report.

> If not, then it's important that all duplicates are resolved as
> Duplicate rather than Fixed.

Yes, that my preference as well.

I usually create a "Duplicates" link between the two issues in JIRA
first and then immediately "Close" the latest issue as "Duplicate".

> 
> Views?
> 
> [1] http://people.apache.org/~sebb/NET_3_0_1RC3/jira-report.html
> Additionally filtered as follows:
> <fixVersionIds>3.0.1,3.0,2.2</fixVersionIds>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org