Skip to end of metadata
Go to start of metadata

The tranSMART Foundation uses the JIRA issue tracker to track issues with the software: https://jira.transmartfoundation.org. Issues with released versions should be created on the 'Release Support' JIRA board. You can click 'Create' on the top of that page to create a new issue report.

JIRA account

To recover or alter your account information, use the tranSMART Foundation's id server: https://id.transmartfoundation.org.
If you don't have an account yet you can obtain one by sending a request to support@transmartfoundation.org with your full name and email address.

Good bug reports

Successful diagnosing and fixing bugs requires accurate, comprehensive and reproducible data. Make sure to include at least these elements:

  • Which version are you using?
    • Include the tranSMART version release number in your report (eg 16.1 or 16.2)
    • If you are using a git checkout, provide the hash of the checked out commit (you can use git rev-parse HEAD for this). If the project is composed of several repositories, include this information for all relevant repositories. If your project requires a build step, make sure that you run this build step after checking out a new version. If in doubt, clean and build project again. If only the latest version/commit is supported, make sure you have updated to that version.
    • If you are interacting with a web application that you did not deploy, provide the time of that interaction instead.
  • What did you do? Include the steps you took to arrive at your error condition. This information should be complete enough so that the person handling the bug can reproduce the problem. This means that, for instance, input files may need to be included as well. If this is a web application, provide also its URL.
  • What did you get? Describe the result you obtained after executing the actions mentioned in the last point. Include all the relevant information you can. This can include full logs, error messages, screenshots, database state and so on.
  • What did you expect? How do the results that you got differ from those that that you expected? If it's not immediately clear that the results you expect are the correct results, provide an explanation for why you think it is the case.
  • No labels