Adds an issue attribute, 'Found in version'. 'Found in version' is the version the issue was found in, and is filled in by the submitter. It can and should only be a single-selection. This field is useful for issue reproduction purposes. You can only select 'locked' versions (in my world, these are versions that have made it past integration and internal release).
#2 Updated by Brian Lindahl over 8 years ago
- stronger validation
- support for bulk edit
- support for move/copy
- support for xml builder
- support for mailer
- db migration (chose date as last migration in 1.0.4 +1 second)
- bug fix for project copy (found version was not copied)
#11 Updated by Brian Lindahl over 8 years ago
- File found-version-1.1.0.patch added
Your SQL-command looks correct for the database migration (the only thing left out was the adding the index - this shouldn't affect anything, as far as I know?).
When I upgraded the patch to support Redmine 1.1.0, it looks like the database migration code (for rake db:migrate) was accidentally left out. I've attached a new 1.1.0 patch that includes the database migration file. Again, the db migration file is set to +1 second after the last database migration in Redmine 1.1.0.
#14 Updated by Mike Spross over 8 years ago
- File found-version-1.1.0.patch added
There's a minor bug in the migration script: the
AddFoundInVersion migration should be renamed to
rake db:migrate errors out due to the mismatch between the migration filename and the class name.
I've added a new version of the patch file with this change (since it was such a minor change I just edited the latest patch file by hand).
#15 Updated by Mike Spross over 8 years ago
Also, I appreciate the time and effort you put into this, Brian. I've also been scratching my head as to why this hasn't be integrated in some shape or form yet into the main project.
However, something I didn't think about until after applying the patch is that since the current implementation adds the "Found in version" directly to the issue model and view, it affects all trackers, which is problematic if you have multiple trackers for a project. At our company, for example, we use Bug, Feature, and Task trackers for all of our projects, but the "Found in version" field only really makes sense for issues filed in the Bug tracker.
I can easily get around this myself by either making the field not required in the view, or adding a hack to only display the field for the Bug tracker, but neither solution is really ideal. I suppose I could also get around it without changing any code by simply adding a dummy version to each project that users can select when creating new Feature or Task issues.
This makes me wonder though if this patch has a better chance of getting integrated if it implements a new custom field type that can be populated with project versions, so that it "plays nice" with multiple trackers (since custom fields can already be enabled or disabled on a per-tracker basis). In other words, something closer to what was originally suggested in #685.
I'm not sure how easy it would be to implement this as a new custom field type, but I will look into this some more and see if I can create a patch that implements it this way. If anyone's interested, let me know.
#17 Updated by Ilia S about 8 years ago
#20 Updated by Brian Lindahl about 8 years ago
I wasn't able to reproduce this problem. Can you give me the details of version 10.3 (status, sharing, owned by project, etc.) as well as the project heirarchy?
If it was a shared version, test a non-shared version? Shared versions work fine in 1.1.0, but things could have changed in 1.1.3. Try it with 1.1.0?
#26 Updated by Roman Yeryomin over 7 years ago
Eric Diaz wrote:
Hi i 'm just trying to install it on 1.3.1. i did some merge manually. All the files and database are ok but i can't see the new field in my screen. There is nothing in the log file. Any Idea ?
you should have at least one locked version there...
if you can make a patch against 1.3 I will be happy to test it
#28 Updated by Eric Diaz over 7 years ago
- File found-in-version-1.3.2-full.patch added
Here is the patch for 1.3.2 (Tested also on 1.3.1).
Don't forget to create the new column in the issues Table.
The issue i encountered previously was not connected to this patch but to the Extra query operators plugin (http://www.redmine.org/boards/3/topics/21015?page=2&r=24993)
#31 Updated by Roman Yeryomin over 6 years ago
Dipan Mehta wrote:
How is this issue any different from #2096, which is already in the release?
It tracks released versions so you cannot choose a version which is not yet released and also which is closed (unsupported).
I see it as having another custom field type - 'version'.
#33 Updated by Go MAEDA over 2 years ago
- File version-type-custom-field.png added
- Status changed from Reopened to Closed
This "Found-in-version" can be realized by using version type custom field.
As of Redmine 2.5.0, we can configure version type custom field to list specific status (open / locked / closed) of versions only. (#8572)