Project

General

Profile

How to create a new change request or issue reporting » History » Version 4

Olivier Bitsch, 11/11/2019 11:36 AM

1 1 Olivier Bitsch
# How to create a new change request or issue reporting
2 2 Olivier Bitsch
3
Whenever you need a new feature or discover an issue from your developed software, you should create a Redmine issue. This will help to track changes and be sure the request will not be lost until the change is implemented and deployed on your platform.
4
5
When you should make a request
6
------------------------------
7
8
You may create a request for any cases listed here.
9
10
* Whenever your discover a security breach (open issue as bug).
11
* Whenever a feature is not working as expected (open issue as bug).
12
* Whenever a feature is not working anymore (open issue as bug).
13
* Whenever you need a new feature (open issue as change request).
14
* Whenever you need the cost estimation for a feature (open issue as change request).
15
16
But you shoudn't create a request for those cases listed here.
17
18
* If your server is not working anymore.
19
* Your computer crashes or is not booting anymore.
20
21 3 Olivier Bitsch
What the process to create a new issue
22
--------------------------------------
23
24
* The first step is accessing to your project page.
25
* Click on the **+** (plus) button on top left of the page.
26
* Click on **New issue**
27
** Choose the appropriate tracker according to the kind of the issue you are going the create.
28
** Choose a clear subjet, like if you send a mail. You may choose something like **New customer field** or **Unable to open page**
29 4 Olivier Bitsch
** ... Process to be finished
30 3 Olivier Bitsch
31 2 Olivier Bitsch
What the next step on issue is created
32
--------------------------------------
33
34
When you create a new request, iabsis team is notified to take care of the issue. We will take a different approach depending of the kind of request.
35
36
* **Issue within software warranty:** if your software is under warranty, your incident will be fixed as soon as possible. Any fee will be invoiced in that case.
37
* **Issue outside of software warranty:** if your software has no warranty cover, we will contact you to check if you prefer renewing your warranty, otherwise your issue will be fixed on man hour basis.
38
* **Change request:** this request will be fixed as man hour basis unless we are actively developing your software. A commercial quotation may be done if required.
39
40
What needs to be done once fixed is done
41
----------------------------------------
42
43
A new package for the software is usually automatically performed in that case. This package needs to be tested first on a staging server and can be then published on your production server.