Reporting Problems

Reporting probems and bugs

If you want to be an active contributer to the process of debugging and refining TRIPS, first please join the TRIPS slack community at https://tripsheadquarters.slack.com there are several important discussion areas to post questions and or clarify the operation of the program to ensure that a problem you're having is a bug.

• general - General discussion about anything about TRIPS
• confused - Discussion about how the program should run if things don't seem to be doing what you think they should
• bug_reports - Discussion about potential bugs to clarify exactly what's wrong.
• data_curaction - Discussion of problems with data when you import a data set

Once you've convinced yourself that you've found a bug then you need to create an issue in github documenting it so that it can be added to the queue of things to be fixed.

• Go to the TRIPS issues page and click the green "New Issues" button.
• Choose an issue template - probably bug report
• Give your new issue a clear, short name/description
• Replace the various sections with your information. Please leave the bold headings ( the lines with ** around them ) alone. Just replace the sample information under the heading with yours.
• Update the check boxes. Move the X for OS version and for TRIPS version to the correct one. (We'll try to change the default to the correct one as the version increments.
• In general, make sure you're running the current version of TRIPS from the release page before creating a bug report.
• Once you've described your bug, chose Labels on the right and select "Bug" as the label.
• Save your bug report as a new issue.