Petals Link's JIRABugs and features requests concerning Petals Studio must be reported on our JIRA. |
Bug // Improvement // New Feature // Task
Once in the studio's category, you have the choice between creating a bug report, an improvement report, a feature request or a task.
Pay attention to the kind of entry to create.
Bugs
A bug is defined as « a problem which impairs or prevents the functions of the product ».
Generally, the definition of a bug is well-understood.
Improvements
An improvement is defined as « an improvement or enhancement to an existing feature or task ».
One example of a new feature would be an extension of the validation made on jbi.xml files (the validation mechanism already exists).
New Features
A new feature is defined as « a new feature of the product, which has yet to be developed ».
One example of a new feature would be the addition of a new editor in the studio (e.g. for XSLT).
Tasks
A task defines « a change that does not impact directly the user ».
One example of a task would be upgrading the version of a parsing library.
Tooling categories
Petals Studio has (for the moment) 4 sub-categories in which you can post tickets.
- Petals Core Tooling includes all the Petals plug-ins, except those for BPEL and SCA.
- Petals BPEL Tooling includes all the plug-ins related to BPEL (creation wizard, sketch export, BPEL Designer, validation...).
- Petals SCA Tooling includes all the plug-ins related to SCA (creation wizards, editors, validation...).
- Studio Product includes all the plug-ins related to the studio itself (e.g. perspective, welcome page, executable), plus the build mechanism.
When you create a JIRA ticket, pay attention to the category for which this ticket fits.
Reporting bugs efficiently
When you report a bug about the Petals Studio, please, be precise.
- Mention the version of the studio, and if you can, mention the build ID too.
This information can be found in the About dialog (Help > About Petals Studio).
- Report the log messages if any.
If a problem occurs, look at the Error Log (Window > Show view > Other... and then General > Error Log).
Post the log details in any bug entry you create on JIRA.