What is an issue?
An issue is a term used to cover any concern, query, request for change, suggestion or off-specification raised within a development project of open-source software (OSS) or semantic interoperability assets. Any registered user of the platform can submit an issue, even without being member of the OSS or asset project. Only projects owners and developers can assign an issue to other members. An issue can be modified by developers, project owners as well as members assigned to the issue.
How can I find a particular issue?
The issue list offers two features to search for a particular issue:
- Keyword search: by filing in the “search for” field, users can provide keywords
- Search filters: by setting the right filters in the “Status”, “Priority”, “Category”, “Version”, and “Component” fields.
The global search feature of the platform also allows retrieving issues across multiple projects.
Who can view an issue?
Any registered users can view an issue.
How to view an issue?
To view an issue:
- Click on the project for which you want to see the issue;
- Click on the “Issue” menu item on the left of the page;
- A search tool and a list of issues will be displayed;
- Use the search tool to find the issue you want to see ;or
- Click on the issue name for entering in the issue you want to see;
- Once you have clicked on the issue name, the issue page will be displayed.
What is displayed on this page?
This page lists the following information for an issue:
- Project: Name of the project
- Version: Project version
- Component: The concerned component type
- Category: The category of the issue
- Priority: The priority of the issue
- Assigned: The software member assigned to this issue
- Status: the status of the issue
- Identifier
All comments and status changes to an issue are listed in chronological order of changes.
Edit an issue
Who can edit an issue?
- Any project member can edit his or her own issues. Modifying an issue is done by adding a comment to it.
- Only the project owner can fully edit issues (e.g. change the status or priority) once created by another project member.
- Each member of a project can take up an issue (assign it to himself) if the issue is unassigned.
- Developer or project owner can assign an issue to any other members.
How to edit an issue?
To edit an issue:
- Click on the project for which you want to edit the issue;
- Click on the “Issue” menu item on the left of the page;
- A search tool and a list of issues will be displayed;
- Use the search tool to find the issue you want to edit ;or
- Click on the issue name for entering in the issue you want to edit;
- Click on “edit” at the top of the page;
Remove/Delete an issue
Who can delete an issue?
Only author of an issue, the project owners, or the facilitators have the right to delete an issue.
How to remove an issue?
In the ‘edit’ mode, an issue can be removed by clicking the ‘delete’ button at the bottom of the page.
Comment an issue
Who can comment on an issue?
Any registered user can comment on an issue
How to comment on an issue?
- Navigate to the issue on which you want to comment;
- Enter your comments in the form at the bottom of the page;
- Press “Submit”.
Is there any good reason to substitute a generic exception by another generic exception?
Is there any reason to request the substitution of a generic exception by anothe rgeneric exception?
The way exceptions are currently defined, the application is forced to catch all exceptions (including run-time exceptions) in order to catch an application-level one, because the Java signature of the exception is the "generic" one ("generic" is to be understood here as a Java technical term). We should keep exactly the same exception handling (from a functional point of view), but replace the "Exception" type by an application-level one - which could be totally generic from a functional point of view, like "SAMLException" - to not mix application-level exception with system-level ones. Furthermore, the SAML engine should not catch run-time exceptions, but only application-level ones.