[ http://issues.apache.org/jira/browse/JDO-363?page=comments#action_12413938 ]
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 leaving the JIRA link on the navbar and adding a new link for this page. However, I don't think that a link called "Issue Tracking" sufficiently distinguishes this page from JIRA. Can we come up with a better name? Maybe "Issues by Release"?? "Issue Status"?? 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 assigned a release on closing. Maybe that was before we got our processes worked out, I'm not sure anymore. 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 and closed issues by release. Must first ake sure that all JIRA issues > have a "resolved 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
