View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0034407 | mantisbt | roadmap | public | 2024-04-19 02:10 | 2024-04-30 04:20 |
Reporter | paspiz85 | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0034407: Options to require target_version and fixed_in_version | ||||
Description | I would need a mechanism to ensure that both 'target_version' and 'fixed_in_version' are always filled in before the bug reaches the Resolved state. The reason is to populate the changelog and roadmap for a specific project. In reality, it would be better to fill in 'target_version' upon reaching the Assigned state, but I believe we need to add a configuration to adjust this behavior. In both situations, if the bug is closed prematurely, it's not necessary to fill in both fields. A simple idea is to assume that 'fixed_in_version' is equal to 'target_version' if one forgets to fill it in during change to Resolved state. Would it be acceptable to simply add checks during the validation of the update? This way, when changing the status that requires a specific field, an error will be returned along with the relevant message. If anyone has any alternatives or suggestions, please write them in the notes. | ||||
Tags | No tags attached. | ||||
related to | 0016774 | new | Ask for the Target version when an issue is confirmed | |
related to | 0013793 | new | Target version change when assign an issue | |
related to | 0011346 | new | Missing 'Target Version' in Closed issue window | |
related to | 0021734 | assigned | community | Resolving issues having a target version should set the fixed in version by default |
related to | 0011551 | new | Fixed In Version should supercede the Target Version entry | |
related to | 0034429 | assigned | community | Options to require fixed_in_version |
Some draft solutions: |
|
These issues have been discussed in the past: |
|
Mandatory fixed in version is now covered by 0034429. @paspiz85 please let me know what we should do with this issue. |
|