Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA/UserDocumentation/IssueTracking"
< VIATRA
Line 12: | Line 12: | ||
* Stating your '''Xtext version''' in the issue description helps | * Stating your '''Xtext version''' in the issue description helps | ||
* If you can, provide steps to reproduce, any workarounds you know of or examples where the bug occurs | * If you can, provide steps to reproduce, any workarounds you know of or examples where the bug occurs | ||
+ | ** You can use our [[VIATRA/ModelObfuscator|Model Obfuscator]] to provide example models that contain sensitive data originally. | ||
== Creating feature request == | == Creating feature request == |
Latest revision as of 04:17, 17 May 2016
Issue Tracking specifics for the VIATRA project
Use Bugzilla or Mylyn to report bugs or create feature requests. For our issue management practices, see here
Reporting bugs
- Select the appropriate component, based on the description in Bugzilla
- Version: Select the one you are currently using, where you found the bug (you can check this in Help -> About Eclipse -> Installation Details)
- Severity: Select one other than "enhancement"
- Write a clear summary
- Stating your Xtext version in the issue description helps
- If you can, provide steps to reproduce, any workarounds you know of or examples where the bug occurs
- You can use our Model Obfuscator to provide example models that contain sensitive data originally.
Creating feature request
- Select the appropriate component, based on the description in Bugzilla
- Version: Select "unspecified", since we don't know if or when it can be added
- Severity: Select "enhancement"
- Write a clear summary
- Provide a real use case for the feature and preferable some examples on how you imagine it