#3042 Additional TPS token state transitions
Closed: migrated 21 days ago by dmoluguw. Opened 2 years ago by edewata.

For completeness, the following transitions should be added into the default token state transitions defined in TPS CS.cfg and token-states.properties:

DAMAGED.PERM_LOST        = This token has been permanently lost.

SUSPENDED.DAMAGED        = This suspended (temporarily lost) has been physically damaged.

TERMINATED.DAMAGED       = This token has been physically damaged.
TERMINATED.PERM_LOST     = This token has been permanently lost.

UNFORMATTED.DAMAGED      = This token has been physically damaged.
UNFORMATTED.PERM_LOST    = This token has been permanently lost.

Metadata Update from @edewata:
- 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1470407
- Custom field type adjusted to None
- Custom field version adjusted to None

2 years ago

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

2 years ago

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

2 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3160

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

21 days ago

Login to comment on this ticket.

Metadata