Difference between revisions of "Bug Tracking"

(Adding email cheatsheet)
m (Replaced content with "=VisIt Issue Tracker= We welcome all VisIt users & developers to participate on our [https://github.com/visit-dav/visit/issues issue tracking system] at GitHub. Categor...")
(Tag: Replaced)
 
Line 1: Line 1:
 
=VisIt Issue Tracker=
 
=VisIt Issue Tracker=
We welcome all VisIt users & developers to participate on our issue tracking system located at https://visitbugs.ornl.gov.
+
We welcome all VisIt users & developers to participate on our [https://github.com/visit-dav/visit/issues issue tracking system] at GitHub.
 
 
To reduce spam we require [https://visitbugs.ornl.gov/account/register registration] with a valid email address. After registering you will receive an email with a link to activate your account. Follow the link and login to complete the process.
 
 
 
VisIt Developers: After you create an account contact Cyrus or Tom to obtain 'Developer' privileges.
 
 
 
== Using redmine ==
 
Our system is an instance of [http://www.redmine.org/ redmine], an open source web based project management application, which allows registered users to:
 
*Submit bug reports and feature requests.
 
*Search for existing issues.
 
*Provide comments & additional info on existing issues.
 
*Monitor the progress of your issues and other issues that interest you via the website, email, and/or RSS feeds.
 
*Monitor which issues are scheduled for each VisIt release via our release Roadmap.
 
*Monitor our repository activity.
 
 
 
=== Submitting issues===
 
When submitting a new issue please select appropriate tracker:
 
*'''Bug''' should be used to file a bug report.
 
*'''Feature''' should be used to request new functionality.
 
 
 
Bug & Feature trackers have their own unique fields selected to help the VisIt team collect necessary info & with prioritization. When you submit an issue try to fill out as may of the fields as possible, but don't worry if you need to rely on default values. Fields used for prioritization will be adjusted by developers as issues are reviewed.
 
 
 
==== Tips for bug submissions ====
 
To help the VisIt team reproduce & diagnose your issue, here is a list of suggested questions to answer with each bug report:
 
*What version of VisIt are you running?
 
*What OS are you running VisIt on?
 
*Are you running in serial or parallel?
 
*Are there simple steps that consistently reproduce the issue?
 
*What type of data are you reading into VisIt?
 
*Which VisIt plots are you using?
 
 
 
If VisIt is crashing please try to generate and attach [[Debug logs]] to the issue submission.
 
 
 
=== Additional VisIt Redmine How-tos & Info ===
 
*[[Redmine Email Submission|Submitting issues via email]]
 
*[[Redmine RSS| Using RSS/Atom Feeds]]
 
*[[Redmine Issue Fields| Issue field details]]
 
*[[Redmine Issue Lifecycle| Issue Lifecycle]]
 
*[[Redmine Reports | Issue Reports]]
 
*[http://www.redmine.org/wiki/redmine/User_Guide Redmine Users Guide]
 
*[[Media:redmine-email-cheatsheet.png | Redmine Email Cheatsheet]]
 
 
 
=== Useful tracker links ===
 
(These also easily accessible when you are logged into the tracker)
 
*[https://visitbugs.ornl.gov/projects/visit/roadmap Release Roadmap]
 
*[https://visitbugs.ornl.gov/my/page "Your Page" (summary of your issue submissions & assignments)]
 
 
 
 
 
[[Open Bug Tracking | Link to our search for an (open) bug tracking solution]].
 
  
 
[[Category: User Documentation]]
 
[[Category: User Documentation]]
 
[[Category: Developer documentation]]
 
[[Category: Developer documentation]]

Latest revision as of 01:47, 27 July 2021

VisIt Issue Tracker

We welcome all VisIt users & developers to participate on our issue tracking system at GitHub.