Details
-
Bug
-
Resolution: Unresolved
-
Major
-
COmanage Registry 4.1.2 (Quiet Quay MR2)
-
None
-
4.1.0 release running in a dockerized container as described in https://spaces.at.internet2.edu/display/COmanage/Building+Registry+Container+Images#BuildingRegistryContainerImages-UsingtheProvidedBuildScript on Ubuntu 20.04.5 LTS.
Description
Using 4.1.0. When approving a petition that has a start date for the role in the future, the status on the role is immediately set to status 'active'.
In our environment appointments may be scheduled to begin at a future date - such as the beginning of an academic term or fiscal year. Our bylaws require accurate start and end dates (accurate to the day) for purposes of authorship and secure access to resources. Therefore, this is critical to our use case.
Furthermore, should there be a special status indicating a role is approved but not yet begun? If not, there needs to be a way to easily identify such role memberships.