You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The view `HELP AND SUPPORT` provides the initial links to get help and support, should you encounter any issues in Code for IBM i.
11
+
The `HELP AND SUPPORT`view provides a link to the documentation, and links to get help and support should you encounter any issues in Code for IBM i.
12
12
13
13
</Card><Card>
14
14
@@ -18,49 +18,65 @@ The view `HELP AND SUPPORT` provides the initial links to get help and support,
18
18
19
19
</CardGrid>
20
20
21
-
### Get started
21
+
### Get started & Documentation
22
22
23
-
This link will open the documentation for Code for IBM i in your browser, making it easy to go directly from Code for IBM i to the information on how to use it.
23
+
This link opens the documentation for Code for IBM i in your browser, making it easy to go directly from Code for IBM i to the information on how to use it.
24
24
25
25
### Open official Forum
26
26
27
-
This link will take you to the Code for IBM i discussions, where you can ask any question on how to use the product.
27
+
This link takes you to the Code for IBM i discussions, where you can ask any question on how to use the product.
28
28
29
29
### Review Issues
30
30
31
-
If you encounter an issue or have a problem that you suspect may be a bug in Code for IBM i, please use this link for the [Issues section](https://github.com/codefori/vscode-ibmi/issues) in the GitHub repository, where you can see all open and closed issue reports created by the users since the start of the project.
32
-
There is a good chance that your problem has been seen before and a solution or workaround found, or a fix may have been created to solve a similar problem.
31
+
If you have a problem, there is a good chance that your problem has been seen before. A solution or workaround may have been found, or a fix may have been created to solve a similar problem. By reviewing the [Issues section](https://github.com/codefori/vscode-ibmi/issues) in the GitHub repository you may be able to solve your issue.
32
+
33
+
You can see all open or closed issues reported since the start of the project and sort them by date.
34
+
35
+

36
+
37
+
You can also search issues by adding text in the search bar:
38
+
39
+

33
40
34
41
### Report an Issue
35
42
36
43
<Asidetype="caution">
37
-
**Do not use the VS Code Issue Reporter (found in Help menu item Report Issue)!**
44
+
**Do not use the VS Code Issue Reporter (found in VS Code Help menu, item Report Issue)!**
38
45
39
46
This issue reporter does not include the configuration and logs necessary to debug your issue, and time will be wasted while the support team will request additional information from you.
40
47
</Aside>
41
48
42
-
If searching existing issue reports using the link above did not give you the solution to your problem, you can create a new issue report using this link.
49
+
If searching existing issue reports did not give you the solution to your problem, the best way to create a new issue report is by using the `Report an Issue` link.
50
+

51
+
This link collects system information about Code for IBM i, the IBM i server and VS Code.
43
52
44
-
<Asidetype="tip">
45
-
Keep your connection to the IBM i system active when creating the issue report (to have all important system information included in the report).
46
-
</Aside>
53
+
It then copies this information into a Github issue and opens the issue for you to complete.
54
+
55
+
#### Steps to create an issue
47
56
48
-
When you click on `Report an Issue` in the `HELP AND SUPPORT` view, your browser will open the GitHub issues page with a template containing the following information:
49
-
- Code for IBM i version, VS Code version and OS
50
-
- Active extensions
51
-
- Remote system information, e.g. IBM i release, TR level, CCSID, enabled features and more
52
-
- Shell environment
53
-
- Variants (used for CCSID troubleshooting)
54
-
- Errors (the last three commands executed on the server and the result)
57
+
To provide the most helpful information for the support staff, follow these steps as far as possible to report an issue:
55
58
56
-
You must also provide a title and thorough description of the issue with information on how to recreate the issue encountered.
59
+
1. Make sure you can reproduce the issue. It is extremely difficult to debug a problem that can't be reproduced.
60
+
2. If the issue is related to some source code, please provide the smallest possible source example that causes the problem and use this when reproducing the issue in the next step. Later, paste the source into the Github issue as **text**. Please do not provide this code as screen shots.
61
+
3. Restart VS Code, connect to the IBM i and immediately cause the problem.
62
+
4. Click the `Report an Issue` link and pick the extension on which to report the issue:
63
+

64
+
5. In the opened Github issue clearly descibe the steps to cause the problem. Paste screen shots if this helps clarify the issue.
65
+
6. Go to the `OUTPUT` tab and select `Code for IBM i`. Select the complete displayed contents and then copy and paste into the Github issue.:
66
+

67
+
7. Click Create to save the issue.
57
68
58
69
<Asidetype="danger">
59
70
All issues are available to the public, so any sensitive information must be redacted before submitting the issue report!
60
71
</Aside>
61
72
62
73
<Asidetype="tip">
63
-
You need to have or create a GitHub account to create an issue report.
74
+
Github allows you to enter text and paste images in an issue. Generally it is not necessary to create separate documents to attach as files.
75
+

76
+
</Aside>
77
+
78
+
<Asidetype="tip">
79
+
You need to have or create a GitHub account to create an issue report. Github accounts are free.
0 commit comments