ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Set %done with issue state while allowing to change %done manually (Feature #331)

Added by Harald Frießnegger at 2011-04-13 09:05 am. Updated at 2012-11-28 10:52 am.

Status:Ready for review Start date:2011-04-13
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:

Description

by default, setting the issue state to closed does not set done to 100.

one can couple %done with the status (can't remember if it was with stock redmine/chili or through a plugin) by telling which state means which percentage.
however, this hides the %done field completely so developers can't document how much work is left for a specific issue.

it would be good to have a configuration option to optionally associate issue states with a value for done whilst still having the possibility to change the value manually.
eg for most users the state closed also means 100 of the work has been done.

History

#1
Updated by Márton Danóczy at 2011-09-29 12:03 pm

+1

To rephrase: even if the issue done field is calculated automatically, it should not be hidden. The user should be allowed to change it. That is, the functionality should be as with the Issue Due Date Plugin

After updating an issue, the following should be checked:
  • If done% is empty, fill it from the automatic values
  • Else
    • if issue status has changed, fill done% from the automatic values
    • if issue status hasn't changed, don't touch done%
  • Target version set to 2.3.0

#2
Updated by Harald Frießnegger at 2011-09-29 12:28 pm

sounds good!

#3
Updated by Holger Just at 2011-10-04 08:32 am

Moving out of the 2.3 target as we don't have any code yet. And I want to release today :)

  • Target version deleted (2.3.0)

#4
Updated by Daniel Nauck at 2012-05-10 01:22 pm

Any news in this topic?

#5
Updated by Stephan Eberle at 2012-05-13 04:35 pm

I added something similar with this Pull Request:

https://github.com/chiliproject/chiliproject/pull/192

Best regards,
Steviee

#6
Updated by Stephan Eberle at 2012-11-19 10:06 am

I added the missing unit tests to Github

  • Status changed from Open to Ready for review

#7
Updated by kwadronaut . at 2012-11-27 09:48 pm

I think Stephans patch is fine, however maybe it should belong in a different bug. To clarify
what's being asked:

After updating an issue, the following should be checked:

If done% is empty, fill it from the automatic values
Else
if issue status has changed, fill done% from the automatic values
if issue status hasn't changed, don't touch done%

What's been written:

After closing a bug, it sets the done ratio to 100%

#8
Updated by Harald Frießnegger at 2012-11-28 09:05 am

kwadronaut is right. the ticket is about some more confguration and functionality. however, setting done to 100% when a ticket is closed already helps a lot and should find it's way into the next release.

#9
Updated by Stephan Eberle at 2012-11-28 10:52 am

Fine by me. Should I do something to speed this up?
Travis-CI seems to have a little problem with my tests, tho... Locally run they work for me.

Also available in: Atom PDF