Redmine

• 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)

You should add your patch to #1675 as well together with the improvements list

I'd rather not maintain multiple issues (since this is also related to #685). All updates to my patch will be stored here. Hopefully the created relation will bring others to this patch issue to get the latest updates.

Unfortunately, after applying the "found-version-1.1.0" patch to the Redmine 1.1.0 sorting and grouping by "target_version" field in issue list stops working.

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.

Can I use the patch added by Mike with Redmine version 1.1.2???

If I use this patch will I be able to update my Redmine to newer versions?

I applied the 1.1.0 patch on Redmine 1.1.3 .

It were no errors during patching, but I am getting Found in version can't be blank error message than creating a new issue. ( obviously, I selected found in version from list)
What can be wrong? Should I downgrade from 1.1.3?

When you create a new issue, you must give it a 'Found in version'. It's a required field in this patch. If you wish, you can change this in
the file 'app/views/issues/_attributes.rhtml'.

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?

First of all, your patch is working fine with 1.1.0!
My test project is simply one project without subprojects, version 10.3 is locked, shared with all projects, owned by test project. Non-shared version does not work also.

Hello!
Very needed patch!
Is this going to be ported to 1.2 version?

+ for this as issue custom field type

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 ?
Regards

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 ?
Regards

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

Thanks Roman.
I can see the field now
But i can't sort issues anymore on query form. I click on apply link and nothing happens.
I'm working on it

How is this issue any different from #2096, which is already in the release?

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'.