Project

Profile

Help

HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...

Bug #918787

can_unit_continue_current_activity() always FALSE with same !present "Activity" requirement.

Added by Sveinung Kvilhaugsvik over 1 year ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
General
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

An activity's action enabler can have a requirement that the actor unit isn't doing the activity right now. can_unit_continue_current_activity() checks if the activity can start. It will then forbid continuing the current activity.

can_unit_continue_current_activity() checks if a unit can do "Fortifying" to see if it still should be "Fortified". But "Fortifying" is illegal for "Fortified" units. (Hard requirement to prevent losing "Fortified" by accidentally giving the order to start "Fortifying")

History

#1 Updated by Sveinung Kvilhaugsvik over 1 year ago

  • Status changed from New to Rejected

I read a bit too fast. I missed that current activity is set to "Idle"

Also available in: Atom PDF