Project

General

Profile

Issues howto » History » Version 35

Alexander Watzinger, 2024-06-25 15:05

1 34
{{toc}}
2
3 35 Alexander Watzinger
h2. Access
4 34
5
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.
6
7 35 Alexander Watzinger
h2. New Issue
8 34
9
* You can create a new issue in a project by clicking on *+ New Issue* in the menu
10
* An issue can be created for a bug, a feature, a question or anything project related you would like to keep track of
11
* Please make sure that your issue hasn't already been reported to avoid duplicates
12
13 35 Alexander Watzinger
h2. Fields
14 34
15
The important ones are *subject* and *description*, when in doubt leave the other fields empty.
16
17 35 Alexander Watzinger
h3. Subject (important)
18 34
19
A short description e.g. "Search function for people"
20
21 35 Alexander Watzinger
h3. Description (important)
22 34
23
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.
24
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:
25
26
* The error message
27
* Which operating system
28
* Which browser/version
29
* A screenshot
30
31
For text formatting you can refer to the Redmine "documentation":https://www.redmine.org/projects/redmine/wiki/RedmineTextFormattingTextile
32
33 35 Alexander Watzinger
h3. Tracker
34 34
35
This field is used to describe the type of issue.
36
37
|Bug|If you found an error.|
38
|Feature|If you want a new feature e.g. you would like a search function for a list view.|
39
|Question|If you want to ask something|
40
|Administration|Administrative tasks e.g. a server upgrade or planning an event|
41
42 35 Alexander Watzinger
h3. Status
43 34
44
Leave on new if it's not yours to work on.
45
46
|New|It's a new issue.|
47
|Acknowledged|It has been seen and accepted.|
48
|Assigned|Someone is assigned to work on it.|
49
|In progress|Someone began working on it.|
50
|Resolved|It's dealt with but not closed, e.g. performance changes but it still has to be tested.|
51
|Closed|The issue has been successfully dealt with. In case the issue isn't solved it will be reopened.|
52
|Rejected|The issue was rejected with an explanation, e.g. it is not possible for technical reasons.|
53
|Duplicate|The issue was already reported.|
54
55 35 Alexander Watzinger
h3. Priority
56 34
57
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.
58
59 35 Alexander Watzinger
h3. Assignee
60 34
61
Choose yourself if you want to work on it, leave it empty otherwise.
62
63 35 Alexander Watzinger
h3. Target version
64 34
65
Leave empty. It's for internal project planning.
66
67 35 Alexander Watzinger
h3. Found in Version
68 34
69
This field is only available for bugs and used to track the version where the bug was found.
70
71 35 Alexander Watzinger
h3. Cooperation
72 34
73 35 Alexander Watzinger
At this field the relevant cooperation might be specified.
74
75
h2. Roadmap
76
77 34
Which features are planned for future releases can be seen on the "Roadmap":/projects/uni/roadmap.
78
Please note that development on the OpenAtlas project is a fluid process and milestones will change depending on factors such as:
79
80
* New feature requests and bug reports
81
* Available resources and funding
82
* Dependencies between issues