The application doesn't enforce that only one cycle has been set as the current cycle. It's also possible to have no cycle set as the current cycle. I'm classifying this as a bug, but it's possible that it might have been by design (for flexibility).
In #116 we noticed that the commitments table on a project page shows the commitments from every cycle that's marked as current. If we were to block multiple "current" cycles then this issue goes away. Otherwise, perhaps the table should only show commitments from the final "current" cycle?
This will need further discussion.
The application doesn't enforce that only one cycle has been set as the current cycle. It's also possible to have no cycle set as the current cycle. I'm classifying this as a bug, but it's possible that it might have been by design (for flexibility).
In #116 we noticed that the commitments table on a project page shows the commitments from every cycle that's marked as current. If we were to block multiple "current" cycles then this issue goes away. Otherwise, perhaps the table should only show commitments from the final "current" cycle?
This will need further discussion.