 |
fixed_in_version too... we have too many users forgetting to fill that in... |
 |
This is a good suggestion, but I know I don't want to manually reset the default version that is used each time a new release comes out. Maybe what is needed is a new release status like "obsolete" and "released"... but it is called "current" or "default"? Also because of the ability to have completely different versions in different projects, this is something that won't really work well in the config file (it'd need an array... and you'd need to update it each time you change version numbers). |
|
|
No, I wasnt thinking of it the config file, but in the project management UI area... Personally, I would rather edit the project every release rather than have to make sure it gets filled in every ticket... have more tickets than releases :wink: |
 |
fixed in version should record the version it'sfixed in - so is more something for admins to choose Similarly, i'd expect an admin would set a target version once they've evaluated the issue |
 |
Hello, Eager to understand if it is indeed possible to have a default setting for Target Version (or the companion fields). I share the same concern that users will neglect to make a selection. Thanks, |
 |
I would like to know when submitting and modifying bugs, TARGET_VERSION can not choose, why is it? TIM20170921215551.png (24,519 bytes) |
- Anonymous
