Issues howto » History » Revision 11
- Table of contents
- New issues
If you have an account you can create a new issue in a project by clicking on "New Issue" in the menu.
An issue (or ticket) can be created for a bug, a feature, a question ... anything project specific you would like to keep track of.
Please make sure that your issue hasn't already been reported to avoid duplicates.
The important ones are subject and description, when in doubt leave the other fields empty. Most use cases are described below.
A short description e.g. "Search function for people"
Describe your request or problem and provide an URL. A lot of information e.g. which version you use is available with just an URL.
If it is a bug the more information the better. e.g. if a button isn't working as expected giving us:
- the error message
- which operating system
- which browser/version
- a screenshot
would be extremely helpful.
For formatting please refer to Redmine documentation
This field is used to describe the type of issue, in most cases it will be bug or feature.
|Bug||If you found an error.|
|Feature||If you want a new feature e.g. you would like a search function for a list view.|
|Administration||Administrative tasks e.g. a server upgrade|
|Refactor||Changes in code that don't change functionality, e.g. changes to improve source code readability|
Leave on new if it's not yours to work on.
|New||It's a new issue.|
|Acknowledged||It has been seen and accepted.|
|Assigned||Someone is assigned to work on it.|
|In progress||Someone began working on it.|
|Resolved||It's dealt with but not closed, e.g. performance changes but it still has to be tested.|
|Closed||The issue has been successfully dealt with. In case the problem still exists it will be reopened.|
|Rejected||The issue was rejected with an explanation, e.g. it is impossible for technical reasons.|
|Duplicate||The issue was already reported.|
In most cases leave it on "low".
Since we have many projects most tickets are on low because the order in which things are done are defined in milestones.
Higher priorities are reserved for issues where immediate action is needed e.g. a site where people have work to do is down.
Leave empty if it's not yours to work on. Choose yourself if you want to work on it.
Leave empty. It's for internal project planning.
Which features are planned for future releases can be seen on the Roadmap
Please note that development on the OpenAtlas project is a fluid process and milestones will change depending on factors such as:
- new feature requests and bug reports
- available resources and funding
- realisation of dependencies between tickets