“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra
This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!
Do not issue bugs reports against versions earlier than 0.9.9.6
Security problem? Check the security section.
Tasklist
FS#1562 - Version fields not updated (default value remains)
| Task Type |
Bug Report |
| Category |
Backend/Core
|
| Status |
Unconfirmed
|
| Assigned To |
No-one
|
| Operating System |
All |
| Severity |
Medium |
| Priority |
Normal |
| Reported Version |
1.0.0 devel |
| Due in Version |
Undecided
|
| Due Date |
Undecided
|
| Percent Complete |
|
| Votes |
0
|
| Private |
No
|
|
Details
Hi!
Let’s say we have two Present versions defined in the Versions List: 1.2.3 and 1.2.4 (beta) and one Future version 1.2.4
In the Fields tab we have the “Reported version” field with “Versions” list assigned. The list is set to “Present” to show only present versions.
We also checked the “Required” option for this field.
Everything is fine but now...
We released a new version and we naturally have to change/update our Versions List. 1.2.3 and 1.2.4 (beta) become Past and 1.2.4 becomes Present.
Unfortunately Fields with the “Required” option checked are not updated. And when you decide to add a new task 1.2.3 remains since it was previously set as default value.
IMO it all works fine for other types of fields but default values of Version fields should be auto-updated if the versions are changed (redefined).
|
Loading...
This is actually the expected behaviour. If you only change a version from "past" to "present", Flyspray will not and should not see a reason to change the default value of the field.