10-20-2010 09:13 AM
10-21-2010 05:36 AM
12-01-2010 10:06 AM
12-02-2010 05:27 AM
01-03-2011 10:02 AM
01-07-2011 04:25 AM
01-07-2011 04:44 AM
Logging and Creating an Issue
Defects are logged in Jira - http://issues.alfresco.com
You should have an account and logging details. If you don’t, open the Login window, and ”Sign up” for an account.
After login, click on “Create Issue” on the top right hand section of the page.
In the field “Project:” select Alfresco
In “Issue Type:” select “Linguistic Bug” when the bug that you are reporting is of linguistic nature. However if the bug is related to a problem of functional nature, please select “Bug”.
This helps to indicate that a bug should be fixed by the engineering team or the translation vendor.
In “Project:” select Alfresco
In “Summary”, please make sure you add the language first e.g. FRENCH – Menu Option Untranslated
Select relevant version: “3.4.” (provided that you installed this version)
Please add any useful information that you consider required with regards to: Environment, Component, etc.
It is very important to give a full description of the linguistic bug so the vendor understands what needs to be fixed.
Or if the bug is of functional nature, the UI team understands the problem.
DEFECT CLASSIFICATION
Alfresco defect classification scheme only uses 'Priority' and not the usual combination of 'Priority' and 'Severity'.
The Priority scale is:Blocker
The scale is used to denote priority for issue resolution, in as much as Blockers should be resolved before Criticals etc. This allows the developers to manage their workload where issues / tasks are spread over many different Alfresco versions.
Critical
Major
Minor
Trivial
Filling information in JIRA:
Please see below some examples on how to report linguistic and functional bugs.
Please make sure you state the language in the title.
For linguistic bugs:
Steps to reproduce:
1. Log into Share
2. Create a folder
3. Option spelling incorrect:
Actual translation:
It says: xxxxxx
Expected result:
It should say: xxxxxx
For functional bugs:
In the “Description” field, indicate the steps to reproduce the bug, the actual result and expected result for example:
Steps to reproduce:
1. Log into JSF as admin;
2. Create any folder with some content;
3. Export folder to any *.acp file and save the package;
4. Log into Share as admin;
5. In RM site create Seria->Category structure;
6. In opened category click Import button;
7. Select the package saved in the 3 step;
8. Click Upload button;
Actual result:
After import all buttons in the category becomes disable; User is not able to import any package anymore;
Expected result:
Friendly notification should be displayed about failed import or folder should be imported successfully
For linguistic bugs:
Steps to reproduce:
4. Log into Share
5. Create any folder with some content;
Actual translation:
It says: xxxxxx
Expected result:
It should say: xxxxxx
Components not localised for this version
The components below have not been localised for this version, therefore any strings coming from these components in Share and Explorer will be displayed in English. Therefore these are not bugs, but please report them for future reference.SharePoint
Records Management
Web Quick Start
Web Project Management (AVM)
Quickr Connector Support
OpenOffice
01-10-2011 09:05 AM
<config>
<client>
<!–
Language selection from login dialog - if false then the language will be selected
from the client browser locale and the language drop-down will not be displayed
–>
<language-select>false</language-select>
</client>
</config>
01-10-2011 09:42 AM
01-10-2011 09:47 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.