Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For expectations, add the ability to customize the expiration time used by the expiration manager #1171

Closed
SamuelHassine opened this issue Jun 30, 2024 · 0 comments · Fixed by #1528
Assignees
Labels
feature use for describing a new feature to develop solved The issue has been solved
Milestone

Comments

@SamuelHassine
Copy link
Member

SamuelHassine commented Jun 30, 2024

Use case

For an expectation, add the ability to customize the expiration time used by the expiration manager for each expectation:

image

@SamuelHassine SamuelHassine added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jun 30, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Aug 22, 2024
@jborozco jborozco added this to the Release 1.7.0 milestone Aug 22, 2024
@EllynBsc EllynBsc self-assigned this Aug 26, 2024
@EllynBsc EllynBsc changed the title For manual expectation, add the ability to customize the expiration time used by the expiration manager Forexpectations, add the ability to customize the expiration time used by the expiration manager Sep 20, 2024
@EllynBsc EllynBsc changed the title Forexpectations, add the ability to customize the expiration time used by the expiration manager For expectations, add the ability to customize the expiration time used by the expiration manager Sep 20, 2024
@RomuDeuxfois RomuDeuxfois added the solved The issue has been solved label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved The issue has been solved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants