Ocean deletion policy | control whether to delete old "deleted" entities
Matar Peles
Examples:
Control whether to:
- delete GitLab PRs that are merged or keep them
- Delete old ArgoCD deployments (based on historyLimit configuration)
- Delete "Done" Jira tasks
The assumption here is that some people would prefer to keep all-time data in Port, and some would rather keep only the live relevant data, so the you should be able to control it.
Matan Grady
Merged in a post:
Retain PR entities after PR is closed.
A
Al-Karim Kerai
Increase the lifespan of Pull request entities ingested using the Azure Devops Ocean Integration. Currently these entities last roughly 7 days from PR close. I'm proposing a way to customise this so that we can set a value for how long they persist. Options could include, 30 days, 3 months, a year, "Don't delete entities on PR close".
This could help aid dashboards that look at closed PR's as currently this data is lost.
Matan Grady
Merged in a post:
Support ingesting merged PRs from Github
Guillaume Hanique
As a healthcare regulated company, I need to be able to see
merged
pull requests that are associated with a JIRA story in Port - and I need to see those PRs dating back since the beginning of time. Currently Port can only ingest
open
Pull Requests, which is not what I need for my regulatory reports.Guillaume Hanique
(This could be implemented with a flag similar to
createMissingRelatedEntities
where, by default, the GetPort.io GitHub App behaves like it has always done).