This repository is dedicated to the creation of issues related to the Reference System Software.
Issues can be EPICs, User Stories, Bugs... that need to be manipulated by the different teams within the development phases.
Once a week, a meeting is held by a dedicated team to review new bugs and assign them to the developers. Existing bugs can also be updated to change the priority for e.g.
When creating a bug, choose the template named ":lady_beetle: Bug User", unless you are from the development, ops and ivv team. If you don't know which template to choose, you are probably an end user, so it's safe to use the ":lady_beetle: Bug User" template. It comes with predefined labels and assignees, please don't change them. The end user shall only edit the content like Environement, Steps To Reproduce and attach evidences (logs and data set).
Before creating a new ticket, please make sure that an existing ticket with the same issue is not already created.
Click here to create a new ticket : GitHub COPRS issues
As this repository is the only source repository for every Zenhub workspaces, labels shall be used in order to classify tickets in the appropriate workspaces. The rule is the following: one label is linked to one workspace.
| Label | Description |
|---|---|
 |
Tickets dedicated to ENG team |
 |
Blocking issue |
 |
Something isn't working |
 |
Issue for CCB |
 |
COTS used in sub-systems |
 |
Change Request |
 |
Ticket dedicated to CS-FRANCE development |
 |
Only bug handling deployment (use%20Epic%20for%20US) |
 |
Something isn't working - internal to dev |
 |
Improvements or additions to documentation |
 |
This issue or pull request already exists |
 |
New feature or request |
 |
Issue type is an epic |
 |
Good for newcomers |
 |
Extra attention is needed |
 |
hmi category |
 |
Infra(structure%20,%20Platform%20and%20basic%20services) category |
 |
This doesn't seem right |
 |
Ticket created by the ivv team |
 |
mon(itoring) category |
 |
Ticket from ADS operation team |
 |
perfo(rmance) category |
 |
Set the priority to blocking because the production is blocked |
 |
Set the priority to major because the production is heavily impacted |
 |
Set the priority to minor because the production is (almost) not impacted |
 |
pro(cessing) category |
 |
Further information is requested |
 |
Issue had been pulled in sprint |
 |
secu(rity) category |
 |
Related to (new) technology |
 |
test(ability) category |
 |
Ticket dedicated to WERUM development |
 |
This will not be worked on |
 |
Workaround activated |
All labels can be found here: https://github.com/COPRS/rs-issues/labels