#3060 UpdateNumberRange: create full range assignment for new clones
Opened 3 months ago by ftweedal. Modified 3 months ago

The idea of a clone delegating part of its assigned range (current or next) to a new clone is, as we see from #3055 (see also PR: https://github.com/dogtagpki/pki/pull/40) a bit fraught. It would be better for the UpdateNumberRange servlet to create a full range assignment for the clone during creation. This probably requires some changes to the UpdateNumberRange API, but is otherwise a straightforward change. It should be implemented in a backwards compatible manner for a future release.


Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

3 months ago

Metadata Update from @ftweedal:
- Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)

3 months ago

Metadata Update from @ftweedal:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

3 months ago

Metadata Update from @ftweedal:
- Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)

3 months ago

Metadata Update from @ftweedal:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

3 months ago

Login to comment on this ticket.

Metadata