• Apache Jackrabbit
  • Welcome
  • Downloads
  • FAQ
  • Jackrabbit Wiki
  • Jackrabbit History
• Documentation
  • Getting Started
  • Standalone Server
  • Jackrabbit Components
  • First Hops
  • JCR & API
  • Jackrabbit Architecture
  • Deployment Models
  • Jackrabbit Configuration
  • Node Types
  • Object Content Mapping
• Development
  • Jackrabbit Team
  • Jackrabbit Roadmap
  • Building Jackrabbit
  • Mailing Lists
  • Issue Tracker
  • Source Repository
  • Continuous Integration
  • Website
  • Creating Releases
  • Attribution
• Apache Software Foundation
  • Introduction
  • Sponsorship
  • Current Sponsors

Issue Tracker

Apache Jackrabbit uses Jira for tracking bug reports and requests for improvements, new features, and other changes.

The issue tracker is available at https://issues.apache.org/jira/browse/JCR and is readable by everyone. A Jira account is needed to create new issues and to comment on existing issues. Use the registration form to request an account if you do not already have one.

See below for guidelines on creating and managing issues.

Issue type

When creating a new issue, select the issue type based as follows:

Issue type	Description
Bug	Bug reports are used for cases where Jackrabbit fails not function as it should (as defined by the JCR specification or some other documentation). If you are not certain whether the issue you've found is actually a bug, please ask the Jackrabbit Mailing Lists first for help.
New Feature	Use a feature request when Jackrabbit does not have some functionality you need.
Improvement	Use an improvement request to suggest improvements to existing features. Typical improvement requests are about updating documentation, increasing stability and performance, simplifying the implementation, or other such changes that make Jackrabbit better without introducing new features or fixing existing bugs.
Test	Use this type when contributing test cases for existing features. Normally test cases should be contributed as a part of the original feature request or as regression tests associated with bug reports, but sometimes you just want to extend test coverage by introducing new test cases. This issue type is for such cases.
Task	Used only for issues related to project infrastructure.

Summary

The issue summary should be a short and clear statement that indicates the scope of the issue. You are probably being too verbose if you exceed the length of the text field. Use the Environment and Description fields to provide more detailed information.

Issue priority

Issue priority should be set according to the following:

Issue priority	Description
Blocker	Legal or other fundamental issue that makes it impossible to release Jackrabbit code
Critical	Major loss of functionality that affects many Jackrabbit users
Major	Important issue that should be resolved soon
Minor	Nice to have issues
Trivial	Trivial changes that can be applied whenever someone has extra time