All LabKey Server development issues are tracked in our Issues List. This is an issue tracker running on our own LabKey Server, which all site users are able to read. For general documentation about issue trackers see Issue/Bug Tracking.


Using the issue tracker provides a number of benefits.

  • Clear ownership of bugs and features.
  • Transparency around assignment of features and fixes to specific releases.
  • Testing of all new features and fixes is guaranteed and documented.

Issue Life Cycle

The basic life cycle of an issue looks like this:

  1. An issue is entered into the issue tracking system. Issues may be used to track features, tasks, bugs, documentation requirements, etc.
  2. The person who opens the issue chooses someone to assign it to, based on feature area ownership or using a "triage" alias created as a catchall.
  3. The assignee of the new issue evaluates it to determine whether it's valid and correctly assigned. Issues may be reassigned if the initial assignment was incorrect. Issues may be resolved as "Not reproducible", "Won't Fix", or "Duplicate" in some cases.
  4. The assignee of the issue completes the work that is required and resolves the issue. If the person who opened the issue ends up fixing it, they should assign the resolved bug to someone else to verify and close. No one should ever close a bug that they have fixed.
  5. The owner of the resolved issue verifies that the work is completed satisfactorily, or that they agree with any "not reproducible" or "won't fix" explanation. If not, the issue can be re-opened. If the work is complete, the issue should be "closed", at which point it will be assigned to "guest" (i.e not assigned to anyone). Issues should only be reopened if the original bug is not fixed. New or related problems/requests should be opened as new issues.

Guidelines for Issues

  1. All users, including guests, can read the public issue list. LabKey staff typically open all issues, including issues opened on behalf of clients.
  2. Include only one topic per opened issue.
  3. Include clear steps to reproduce the problem, including all necessary input data.
  4. Indicate both the expected behavior and the actual behavior.
  5. If an exception is described, include the full stack trace in text form (e.g., copy the text from the log file or the web page, as opposed to a screen shot).

Premium Edition Users

Subscribers to LabKey Premium Editions have similar private issue trackers provided on their individual client support portals. Clients can either open their own issue reports or submit requests in concert with their account manager.

Related Topics


Was this content helpful?

Log in or register an account to provide feedback

expand all collapse all