commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Updated: (JELLY-52) provide correct bug reporting link on jelly web site!
Date Tue, 09 Sep 2003 15:54:10 GMT
The following issue has been updated:

    Updater: Morgan Delagrange (mailto:mdelagra@yahoo.com)
       Date: Tue, 9 Sep 2003 10:53 AM
    Comment:
The fact that the Jira bug tracking has no official ties to Apache is a known issue, and I
don't know that we can link to it from that particular page.  Wrt. bug tracking being too
buried on the main Jelly page, I wholeheartedly agree.
---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-52&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-52


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-52
    Summary: provide correct bug reporting link on jelly web site!
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 5 minutes

    Project: jelly
 Components: 
             documentation
   Fix Fors:
             1.1-beta-1

   Assignee: 
   Reporter: Ralf Hauser

    Created: Wed, 21 May 2003 10:42 AM
    Updated: Tue, 9 Sep 2003 10:53 AM

Description:
the currently available link under "Jakarta Community" lead me to bugzilla: --> http://jakarta.apache.org/site/getinvolved.html,
-->
http://jakarta.apache.org/site/bugs.html

It is not that obvious to look for "Project Documentation" - "Project Info" - "Issue Tracking"
I would guess that QA deserves a top-level link?


I have also suggested to bugzilla to close Jelly for input --> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20120


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message