Implement getInAppUrl definition for rules saved object#252782
Merged
MichelLosier merged 7 commits intoelastic:mainfrom Feb 17, 2026
Merged
Implement getInAppUrl definition for rules saved object#252782MichelLosier merged 7 commits intoelastic:mainfrom
MichelLosier merged 7 commits intoelastic:mainfrom
Conversation
Contributor
|
This could use some function tests:
|
Member
|
@baileycash-elastic @dominiqueclarke something for us to keep track of that we will now need to update when we yank the rule UI consolidation feature flag soon |
jeramysoucy
approved these changes
Feb 12, 2026
Contributor
jeramysoucy
left a comment
There was a problem hiding this comment.
LGTM! I tested the SO management page and confirmed the behavior as expected.
Contributor
Author
kapral18
approved these changes
Feb 13, 2026
Contributor
💔 Build Failed
Failed CI StepsMetrics [docs]
History
|
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
Feb 19, 2026
Resolves: elastic/ingest-dev#6716 Adds a `getInAppUrl` definition for the rule saved object, which defines where to view the rule in the UI. This is used by the Saved Objects management view, and the integrations assets view. This relies on the re-routing behavior from `/app/management/insightsAndAlerting/triggersActions` to `/app/rules` controlled by the `unifiedRulesPage` flag as implemented in: elastic#250493
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
Resolves: elastic/ingest-dev#6716 Adds a `getInAppUrl` definition for the rule saved object, which defines where to view the rule in the UI. This is used by the Saved Objects management view, and the integrations assets view. This relies on the re-routing behavior from `/app/management/insightsAndAlerting/triggersActions` to `/app/rules` controlled by the `unifiedRulesPage` flag as implemented in: elastic#250493
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves: https://github.com/elastic/ingest-dev/issues/6716
Adds a
getInAppUrldefinition for the rule saved object, which defines where to view the rule in the UI. This is used by the Saved Objects management view, and the integrations assets view.This relies on the re-routing behavior from
/app/management/insightsAndAlerting/triggersActionsto/app/rulescontrolled by theunifiedRulesPageflag as implemented in: #250493To test:
With both the unifiedRulesPage flag on and off
Saved Objects management:
app/management/kibana/objectsIntegration assets:
app/integrations/detail/elastic_agent-2.7.0/overviewAll links should route to the detail view of the rule.
Before

After

Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.