Issue submission requirements

Random topics about any and everything
User avatar
Site Admin
Posts: 20768
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk

Issue submission requirements

Post by martin@rootjazz » Mon Jul 13, 2015 2:22 pm

When submitting a bug / issue you are having. The following arerequired.

What program and version are you using do check if there is an update:

Please describe your issue:

Describe what is going wrong:

Describe what was expected:

Describe the steps to replicate your issue. A list of instruction steps, include all inputs / options you set (screenshots can be useful here)

If you are setting any specific options for the action, detail those.

Include the processing logs, that show your issue (processing logs are shown when you double click the action in the processing tab

Submit your logs and note the logs ID: the first 4 numbers is sufficient (displayed after successful uploading of logs).
NOTE, your logs need to be submitted after the issue (not a day / week after. If you can isolate the issue, this will lead to a quicker resolution of your problem. By this, run an isolated action to generate the issue. Do not run any other actions, use a single thread, do not do anything else during or after the action that causes your issue, then submit logs straight away

To submit your logs, in the app


Please do not assume anything. Things that seem obvious to you, as you are running the action will not be to others. When describing the action, please make sure you not everything about it, the options you select, the filter you specify. 9/10 the issue is not with the action itself, but the combination of options selected, the flow the program takes due to all those options.