...
| Excerpt |
|---|
Issues are Tracked in GitHubThe PBS issue tracker is at https://github.com/pbspro |
...
To File a Bug or Feature Request
- Log in to https://pbspro.atlassian.net
- Click on the Create button
- Choose "Bug", "RFE", or "User Story"
- Fill in the title and description as follows:
Bug title
- Use 50 characters or less
- Provide a clear, concise summary of the problem as it affects the customer
Component
- In the "Component" field, specify whether it is against PBS Pro code, a design document, or an automated (PTL) test.
Affects Version(s)
- Specify the earliest PBS version affected
Bug description
...
But it might exist there already... see if you can find it. Filing a Bug or Feature Request (RFE)Bug?In a few words, how does it affect the software user? What are the steps to reproduce the problem? If the issue is intermittent and not easily reproducible, |
...
what triggers it? It's helpful to add the platform where the bug is observed, for example CentOS 7.2 Make it easy to understand and reproduce the problem that the |
...
user sees. You can include short illustrative excerpts from log files or terminal sessions. Do not include large sections of log files or terminal sessions |
...
. Useful Attachments |
...
Output of the $PBS_EXEC/sbin/pbs_snapshot command, or the $PBS_EXEC/unsupported/pbs_diag command |
...
Log excerpts, core files, or terminal sessions to help the developers to analyze the bug more easily RFE |
...
Provide a clear, concise summary of the requested capability or functionality
RFE or User Story description
- Provide a clear description of the requested capability or functionality. Don't leave your reader guessing. Don't leave the description empty.
- Provide a clear description of each use case
?Describe the new feature. How does it make the world a better place? The new feature may already be in the works. You can look through the project documentation pages to find out. Thanks! |