[ [url]http://issues.apache.org/jira/browse/JDO-363?page=comments#action_12413938[/
url] ]

Michelle Caisse commented on JDO-363:
-------------------------------------

Thanks for your comments, Michael and Craig.

I agree that Issue Tracking is better than Bug Tracking.  I am fine with lea
ving the JIRA link on the navbar and adding a new link for this page.  Howev
er, I don't think that  a link called "Issue Tracking" sufficiently distingu
ishes this page from JIRA.
Can we come up with a better name?  Maybe "Issues by Release"??  "Issue Stat
us"??

Re Michael's question 2, the navbar that shows on the attached html page is 
in a separate source file which I have not yet modified, pending a decision 
on the name(s) of the link(s).

I fixed the typos in the *final* filter names.

I used the verbose  "Issues resolved and closed as fixed in ..." rather than
 Craig's more elegant  phrasing because I thought we, by convention, only as
signed a release on closing.  Maybe that was before we got our processes wor
ked out, I'm not sure anymo
re.  In any case the two "Issues Resolved..." filters only show issues that 
are closed, not ones that are merely resolved.  Should I change that?



> Add links to site to JIRA filters for open and closed issues by release
> -----------------------------------------------------------------------
>
>          Key: JDO-363
>          URL: http://issues.apache.org/jira/browse/JDO-363
>      Project: JDO
>         Type: Task

>   Components: site and infrastructure
>     Reporter: Michelle Caisse
>     Assignee: Michelle Caisse
>  Attachments: bugtrackiing.html
>
> Add links from the JDO web site to the JIRA page to  do calculations of the open a
nd closed issues by release.  Must first ake sure that all JIRA issues have a "resol
ved in release" entry.  Might have to reopen some JIRA issues just to add this info.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]

[ Post a follow-up to this message ]

Maybe we should be using JIRA's Change Log
(http://issues.apache.org/jira/brows...changelog-panel)
and Open Issues
(http://issues.apache.org/jira/brows...penissues-panel)
features instead of the filters that I made.  This implies that we
should use the workflow that Doug Cutting described:

> In Hadoop we close issues when a release is made.  This makes Jira's
> "Change Log" feature work better, since folks shouldn't generally
> change an issue after it has been released, as that will alter the
> release's change log, which should be read-only.  We encourage folks
> to not re-open closed bugs but instead to create new bugs referencing
> closed bugs that can be tracked in an upcoming release.  Perhaps we
> should even alter the workflow so that closed issues cannot be re-opened.


In that case, we can simply add a link called "Change Log" to the
navbar. Maybe we should change the current JIRA link URL
(http://issues.apache.org/jira/secur...t.jspa?id=10630) to
the Open Issues URL, since the current (Browse Project) URL seems to use
cookies to open to the JIRA page you viewed in your last browser session
(Open Issues, Road Map, Change Log, or Popular Issues).

-- Michelle

Craig L Russell wrote:

> Hi Michelle,
>
> On May 30, 2006, at 4:49 PM, Michelle Caisse (JIRA) wrote:
> 
>
>
> Issue Status by Release? Or is that too long?
> 
>
>
> I think that was before we were completely clear on the process. But
> now I don't know that we have decided when issues get closed.
>
> Anyway, I think that accuracy would be "Issues resolved in..."
> instead of "closed in...".
> 
>
>
> When should issues be closed? I'll file a question to the JIRA
> experts and let this alias know what I get back.
>
> Craig
> 
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>

[ Post a follow-up to this message ]