JSecurity

We are happy to use and provide the JIRA bug and issue tracking application for bugs, tasks, feature requests, and other issues related to JSecurity development. We thank Atlassian for supporting JSecurity by contributing their fantastic product to our project.

Jira Usage Guidelines

Jira is provided as a JSecurity software development resource. It is meant to be for managing bugs, tasks and improvements in the software itself - it is not a support portal to ask for advice or help. For community advice and help in using JSecurity, please visit our Support section.

Prior to using Jira, we ask that:

• You do your due diligence to ensure a suspected error is actually a bug.
• You search the issue tracker to ensure what you want to report has not already been reported by someone else.
• If your problem is actually a bug, we would appreciate it if you could attach a simple JUnit test case that allows us to repeat the problem so we can fix it as fast as possible
• If a unit test is not available (please really try to make one!), attach a stack trace and JSecurity's Log4J TRACE or DEBUG output.
• If you've already fixed the problem, please submit a patch and we'll likely include it in the next release.

You may browse JIRA anonymously, but you must register as a Jira User*** to submit, track, or vote on issues.

 

 Click Here to use the Issue Tracker:

--> JSecurity JIRA Issue Tracker <--

 

*** Because Jira is a seperate product and not integrated into the software that runs this website, you'll need to explicity register for Jira, even if you're already a JSecurity User.  Sorry for this minor inconvenience, but Jira is worth it!