-
Notifications
You must be signed in to change notification settings - Fork 95
Using the Issue Tracker
IMPORTANT: Please review our our Communications Guidelines document before posting on the GitHub Issue Tracker.
Each BUILD module on GitHub has an Issue Tracker. This page describes how to do the following:
- Labels in BUILD Issue Trackers.
- Report Bugs In the the Issue Tracker
- Ask Questions Using the Issue Tracker
- Propose Enhancements the Using Issue Tracker
- Links to BUILD module Issue Trackers
###Report Bugs In the Issue Tracker
Follow these steps to report a bug you've found in BUILD:
- Before you report a bug, ensure that it is:
- A real, current bug
- Not a duplicate
- Reproducible
-
To report a bug, click the New Issue button in the Issue Tracker of the relevant module.
-
Apply the
Buglabel to the issue by clicking the cog symbol in the Labels panel on the right of the page and selectingBug. -
You can highlight issues you create in the Issue Tracker for the attention of a specific person by adding # and the relevant GitHub user name / identifier to the title of the issue. GitHub usernames are displayed in parentheses in the table below. If you do not identify a specific user, your issue is assigned to the most appropriate member of the team. To identify team member of individual BUILD modules, click here.
-
We prioritize bugs reported as follows:
- A good summary is provided.
- The bug is well-documented.
- A minimal example (with screen shots if applicable) is provided.
- The recommended bug template is used.
-
Enter a title that summarizes the issue, so that at a glance the community can identify whether it may be relevant to them. For example, if reporting that a feature on the Projects UI is displaying incorrectly, use 'Display issue with Projects UI', rather than 'UI Issue'. In addition, if the issue is related to a particular backlog item, please include the backlog issue number in the title.
-
Enter a summary is specific to the bug.
-
Click the Submit Issue button.
To review the complete guidelines for reporting bugs, see Guidelines for Bug Reports.
Once an issue has been created, you can click comment to add further comments or respond.
###Ask Questions Using Issue Tracker
Questions can be general, or can be proposals for new features. To create a question in the Issue Tracker:
-
Click the New Issue button in the Issue Tracker of the relevant sub-project.
-
Apply the
Questionlabel to the issue by clicking the cog symbol in the Labels panel on the right of the page and selectingQuestion. -
You can highlight issues you create in the Issue Tracker for the attention of a specific person by adding # and the relevant GitHub user name / identifier to the title of the issue. GitHub usernames are displayed in parentheses in the table below. If you do not identify a specific user, your issue is assigned to the most appropriate member of the team. To identify team member of individual BUILD modules, click here.
-
Ensure the summary reflects the essence of your question, to enable community members to identify if it is relevant to them.
-
Click the Submit Issue button.
Once an Issue has been created, you can click comment to add further comments or respond.
###Propose Enhancements Using Issue Tracker
-
New feature or enhancement proposals can be created using the GitHub Issue Tracker for each sub-project.
-
Apply the
Feature Enhancementlabel to the issue by clicking the cog symbol in the Labels panel on the right of the page and selectingFeature Enhancement. -
You can highlight issues you create in the Issue Tracker for the attention of a specific person by adding # and the relevant GitHub user name / identifier to the title of the issue. GitHub usernames are displayed in parentheses in the table below. If you do not identify a specific user, your issue is assigned to the most appropriate member of the team. To identify team member of individual BUILD modules, click here.
-
Click the Submit Issue button.
Once an issue has been created, you can click comment to add further comments or respond.
##Links to BUILD Module Issue Trackers
Foundation Module Issue Trackers
- angular-sap-common-directives module Issue Tracker
- angular-sap-common-services module Issue Tracker
- angular-sap-ui-elements module Issue Tracker
- angular-sap-common-filters module Issue Tracker
- node-sap-mongo-config module Issue Tracker
- node-sap-common module Issue Tracker
- node-sap-app-server module Issue Tracker
- node-sap-mailer module Issue Tracker
- node-sap-secure-store module Issue Tracker
- node-sap-upload module Issue Tracker
- node-sap-mongo
- node-sap-promise module Issue Tracker
- node-sap-logging module Issue Tracker
- node-sap-mongo-config module Issue Tracker
- node-sap-build module Issue Tracker
- angular-sap-html2canvas module Issue Tracker
- angular-sap-d3-plugins module Issue Tracker
Build Module Issue Trackers
- BUILD_PrototypeEditors module Issue Tracker
- BUILD_Projects module Issue Tracker
- BUILD_UICatalogManager module Issue Tracker
- BUILD_UserResearch module Issue Tracker
- BUILD_BusinessCatalogManager module Issue Tracker
- BUILD_Auth module Issue Tracker
- BUILD_Shell module Issue Tracker
- BUILD_SharedThirdParties module Issue Tracker
- BUILD_Common module Issue Tracker
- BUILD_AngularUIGrid module Issue Tracker
- BUILD_AngularUIGridTree module Issue Tracker
- BUILD_AngularUIGridZip
- BUILD_KeyBoardEventPolyfill module Issue Tracker
- BUILD_jQuery module Issue Tracker
Admin Module Issue Trackers