Issues howto » History » Revision 35
Revision 34 (Alexander Watzinger, 2024-06-17 16:42) → Revision 35/37 (Alexander Watzinger, 2024-06-25 15:05)
{{toc}}
h2. h1. Access
To create an issue you'll have to be a registered user. You can create an account at https://redmine.openatlas.eu/account/register. It will take a few hours up to a few days to get activated.
h2. h1. New Issue
* You can create a new issue in a project by clicking on *+ New Issue* in the menu
* An issue can be created for a bug, a feature, a question or anything project related you would like to keep track of
* Please make sure that your issue hasn't already been reported to avoid duplicates
h2. h1. Fields
The important ones are *subject* and *description*, when in doubt leave the other fields empty.
h3. h2. Subject (important)
A short description e.g. "Search function for people"
h3. h2. Description (important)
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 providing the following would be very helpful:
* The error message
* Which operating system
* Which browser/version
* A screenshot
For text formatting you can refer to the Redmine "documentation":https://www.redmine.org/projects/redmine/wiki/RedmineTextFormattingTextile
h3. h2. Tracker
This field is used to describe the type of issue.
|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.|
|Question|If you want to ask something|
|Administration|Administrative tasks e.g. a server upgrade or planning an event|
h3. h2. Status
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 issue isn't solved it will be reopened.|
|Rejected|The issue was rejected with an explanation, e.g. it is not possible for technical reasons.|
|Duplicate|The issue was already reported.|
h3. h2. Priority
This field is not in use, since the priority of issues is determined through their placement in the roadmap. However, because this field can't be removed in Redmine it is still available and "normal" is the only available option.
h3. h2. Assignee
Choose yourself if you want to work on it, leave it empty otherwise.
h3. h2. Target version
Leave empty. It's for internal project planning.
h3. h2. Found in Version
This field is only available for bugs and used to track the version where the bug was found.
h3. Cooperation
At this field the relevant cooperation might be specified.
h2. h1. Roadmap
Which features are planned for future releases can be seen on the "Roadmap":/projects/uni/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
* Dependencies between issues
h1. Cooperation
At this field the relevant cooperation might be specified.