Redmine

• "can decide it the log time form what to updated or not the issue" -> "can decide in the log time form to update or not the issue"
• "issue remaining time with be decreased" -> "issue remaining time will be decreased"

+5!

Marius, these patches look great! Unfortunately they don't apply cleanly to Redmine 3.3.2, 3.3.1 or to `master`. If you have a git branch and publish it, I could help with rebasing. Would love to see this make it into core.

Kosta H wrote:

Marius, these patches look great! Unfortunately they don't apply cleanly to Redmine 3.3.2, 3.3.1 or to `master`. If you have a git branch and publish it, I could help with rebasing. Would love to see this make it into core.

I'll upload a new version of the patches after the release of Redmine 3.4.0.

Thanks so much Marius! Could the maintainers please weigh in on whether this might make it into 3.4.x or 3.5.x? I'd very much like to use these patches on my organization's Redmine instance but am hesitant to without knowing if they'll make it into the upstream branch.

This is exactly the feature I am looking for.

Apologies for the naive question. Will this feature work for Redmine 3.3.3.stable? That is the version we are currently using.

Sudeep Halappa wrote:

This is exactly the feature I am looking for.

Apologies for the naive question. Will this feature work for Redmine 3.3.3.stable? That is the version we are currently using.

I didn't tests the patches against 3.3.3.stable, but you could try to apply the first version (uploaded by me in 2016).

+1

Marius, are you still determined to have this feature added? I'm evaluating if we should should apply the patch to our own instance but will avoid if we have to maintain it for all future versions.

If so, do you plan to provide a patch for 4.1?

Anders Thomsen wrote:

Marius, are you still determined to have this feature added? I'm evaluating if we should should apply the patch to our own instance but will avoid if we have to maintain it for all future versions.

Yes, I still think that it's a good improvement for Redmine, but the decision is at Jean-Philippe.

If so, do you plan to provide a patch for 4.1?

4.1 for sure, but I cannot say about other future versions.

This feature looks nice. We want to be able to say how much work it remains to close a specific version of our software. I hope this will be included in a future Redmine release. Thank you.

Marius BALTEANU wrote:

Anders Thomsen wrote:

Marius, are you still determined to have this feature added? I'm evaluating if we should should apply the patch to our own instance but will avoid if we have to maintain it for all future versions.

Yes, I still think that it's a good improvement for Redmine, but the decision is at Jean-Philippe.

If so, do you plan to provide a patch for 4.1?

4.1 for sure, but I cannot say about other future versions.

Is this feauture ever going to added to 4.2?
Or is there a 4.2 compatible version of the patch?
This is the only thing which is holding us back updating to 4.2 at the moment.

+1

Is there any update on this ?

We need a way to know both the full time (Estimated Time) - which is best current estimate, and is used in conjunction with % done om the Agile plugin for charts (burndown)

And the remaining time, for planning

(and somehow we also need to keep the original estimate as a "baseline" - we have this as a custom field currently)

Radek Pesina wrote in #note-27:

Hi,

This is a feature that would be very handy to exist in Redmine! I've had a go at updating the patchsets to the latest version of Redmine (v5.1.2) - they appear to work on my local instance of redmine.

Hello Radek,
i'd like to know, i don't know if you have a little amount of time to update this for 5.1.3? it could be really great! i couldn't install the 5.1.2 with bitnami as they give only the last update on their site... i really need this functionnality and as i said could be really great if you could lend me some help!
Thanks in advance!
Cordially.