Add links to site to JIRA filters for open and closed issues by release

• Key: JDO-363
• Type: Task
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Michelle Caisse
• Reporter: Michelle Caisse
• Component/s: site and infrastructure

Description

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.

Comments

[Michelle Caisse]

I have created the JIRA filters to which we can link from the JDO web site. Please check them out to see if the search criteria are the ones we want:

JDO2finalFixed http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310836

JDO2finalOpen http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310839

JDO2maintenance1Fixed http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310837

JDO2maintenance1Fixed http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310838

[Michelle Caisse]

Please review the attached web page linking to JIRA and to the filters. I propose replacing the link called "JIRA" on http://db.apache.org/jdo/* with a link called "Bug Tracking" that points to the attached page.

[Michael Bouschen]

The page looks good, just two comments:
(1) Should we call the page "Issue Tracking" instead of "Bug Tracking"? You can add improvements and tasks to JIRA which are not necessarily bugs. Chaning this would include the name of the html file, the title and the text of the link on the other pages.
(2) The page itself has a link called "JIRA" in the menu under Development. Do ypu plan to change this link, too?

I don't know that we should replace the JIRA entry in the left navbar. How about we add "Issue Tracking" to the navbar but leave JIRA?

The names seem to include the numeral 0 instead of the letter O in JD02finalOpen and JD02finalFixed.

I agree with Michael that we should call these filters "Issue Tracking".

The text "Issues resolved and closed as fixed in ..." should probably be more simply and accurately "Issues resolved as fixed in ...".

Regarding the link called JIRA in the "Issue Tracking" page itself, it should remain as it is.

[Michelle Caisse]

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?

[Craig Russell]

Based on feedback we got from other Apache projects, I propose we use the following workflow for our JIRA issues.

Open<->Resolved->Closed

When the engineer has fixed an issue, she sets the issue to resolved. The submitter can reset it to open if there is some problem with it. When the release in which the issue is fixed ships, the issue is set to closed.

If the same issue comes up again after release, another JIRA is opened, referring to the original issue. This accommodates fixes being backported (if ever necessary) to dot releases after the original release ships.

This workflow can be elaborated to add more steps between open and resolved but for now that seems unnecessary.

With this change, we can use JIRA features to track changes by release and automatically generate release notes.

[Michelle Caisse]

This makes sense. I propose that we simply add a link called Change Log to the navbar of db.apache.org/jdo that links to the JDO JIRA change log (http://issues.apache.org/jira/browse/JDO?report=com.atlassian.jira.plugin.system.project:changelog-panel). We should also change the existing JIRA link to point to the JIRA Open Issues page (http://issues.apache.org/jira/browse/JDO?report=com.atlassian.jira.plugin.system.project:openissues-panel). The existing link goes to one of Open Issues, Road Map, Change Log, or Popular Issues, depending on which was opened in the last browser session.

I think this meets the requirements implied by this issue. I will then delete the filters and not check in the attached page.

[Craig Russell]

I like everything you have proposed here.

Just one more one more.

Is there a good place to add http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12310830&styleName=Html&projectId=10630&Create=Create to the web site

[Craig Russell]

I like everything you have proposed here.

Just one more one more.

Is there a good place to add http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12310830&styleName=Html&projectId=10630&Create=Create to the web site

And we need a place to put our "new, improved" process. Would it make sense to add a "JIRA" web page with the process, linked from the left navbar JIRA that has the workflow plus the links you mention above?

[Michelle Caisse]

I think a new page is a good idea (again). See the attachment. One minor issue with the proposed workflow: when you reopen a bug, its status is "reopened". So I changed the workflow diagram and description.

[Craig Russell]

Cool. Ship it.

[Michelle Caisse]

The web pages have been checked in with revision 410660 and are available on the web. Hit reload to clear the old pages from the cache and see the new "Issue Tracking" link on the navbar.