Content
View differences
Updated by Marc Alcobé 12 months ago
###
### Steps to reproduce
First log as member or admin and add a new work package, you will see that the priority field is filling by itself with the default value ex: NORMAL and keep it in mind.
Log as Admin, go to the priority field editor in the work package section.
Delete the default value that was pushed earlier.
Now go add a new work package again and you will need to enter the priority manualy. for simple work package its ok but when you try to add some from the "add children" in a work package it block you to do it because it need the field.
When you go back to the priority filed editor, _**you can't**_ set a priority by default and the program dosen't set a new by itself.
<br>
### Temporary solution
The only work around i found was to backup the platform, edit the .sql file to add a "true" at the desired field to "is\_default" manualy and then restore the database.
`<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/633553/content">`
### Desired behaviour
* Add a "Default" check box to the form for creating/editing priorities
* The check box is placed below the "Active" checkbox
* Add \[open\] Do we need a caption on the checkbox explaining that checking this will deselect the "Default" value from any other priority currently being the default priority.
priority?
* \[proposal\] Making this value default will override the previous default value.
* When saving a priority with the "Default" checkbox checked, other priorities currently being marked as the default priority will loose that characteristic.
* On the list of priorities in the administration, add a "Default" text to the one priority, being the default. This should look similar to how it is displayed for project phases: <img phases:<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/660099/content" alt="Ignore the fact that the color indicator is not displayed here, it is just a mock-up">
<br>
### Environnement
Tested on v15.5.1 and v16, running on docker compose
Selfhosted on ubuntu 24.04 LTS
Tested with firefox and Chrome
**Language**
_English and French_
### Steps to reproduce
First log as member or admin and add a new work package, you will see that the priority field is filling by itself with the default value ex: NORMAL and keep it in mind.
Log as Admin, go to the priority field editor in the work package section.
Delete the default value that was pushed earlier.
Now go add a new work package again and you will need to enter the priority manualy. for simple work package its ok but when you try to add some from the "add children" in a work package it block you to do it because it need the field.
When you go back to the priority filed editor, _**you can't**_ set a priority by default and the program dosen't set a new by itself.
<br>
### Temporary solution
The only work around i found was to backup the platform, edit the .sql file to add a "true" at the desired field to "is\_default" manualy and then restore the database.
`<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/633553/content">`
### Desired behaviour
* Add a "Default" check box to the form for creating/editing priorities
* The check box is placed below the "Active" checkbox
* Add
* When saving a priority with the "Default" checkbox checked, other priorities currently being marked as the default priority will loose that characteristic.
* On the list of priorities in the administration, add a "Default" text to the one priority, being the default. This should look similar to how it is displayed for project phases: <img
<br>
### Environnement
Tested on v15.5.1 and v16, running on docker compose
Selfhosted on ubuntu 24.04 LTS
Tested with firefox and Chrome
**Language**
_English and French_