feat(ra): Move Risk Acceptance from Engagement to Product level #13780
+740
−444
Conversation
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
Contributor
kiblik
commented
Nov 26, 2025
kiblik
commented
- Changed Risk_Acceptance relationship from Engagement (ManyToMany) to Product (ForeignKey)
- Created dedicated risk_acceptance module separate from engagement
- Simplified URLs to use only risk acceptance ID without requiring product/engagement ID
- Added dedicated Product-level Risk Acceptance UI page with navigation tab
- Created 3 separate migration files (0249, 0250, 0251)
- Updated all templates, views, API serializers, and tests
github-actions
bot
added
New Migration
kiblik
force-pushed
the
feature/risk-acceptance-product-level
branch
7 times, most recently
from
63eff98 to
424e179
Compare
- Changed Risk_Acceptance relationship from Engagement (ManyToMany) to Product (ForeignKey) - Created dedicated risk_acceptance module separate from engagement - Simplified URLs to use only risk acceptance ID without requiring product/engagement ID - Added dedicated Product-level Risk Acceptance UI page with navigation tab - Created 3 separate migration files (0249, 0250, 0251) - Updated all templates, views, API serializers, and tests - Adapted to upstream/dev structure with asset/urls.py instead of product/urls.py - Fixed function name from _copy_model_util to copy_model_util for upstream/dev compatibility Signed-off-by: kiblik <[email protected]>
kiblik
force-pushed
the
feature/risk-acceptance-product-level
branch
from
424e179 to
43c2b07
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.