Project

General

Profile

Actions

User story #4187

open

Allow more granular check for Change Request merge test

Added by François ARMAND over 10 years ago. Updated about 6 years ago.

Status:
New
Priority:
2
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Today, we don't allow to commit a Change Request if the current state of the object contained in the change request has changed compared to when the change request was created.

That leads to "unmergeable" Change Request in case like "the description of the rule changed, but my change request try to add a directive in it - nothing conflicting here".

The goal of that user story is to allow such change requests.

More preciselly, we want to allow a change request if
- no field in an object of the change request has changed since its creation and also allow changes in a non-conflicting way (for exemple, if the name changed as requested by the change request or if we added an other directive in the rule)
- then, allow a more granular control for directive parameters, so that the change request is not mergeable only if the same parameter, in the same (multi-)valued section, changed in a conflicting way.


Subtasks 2 (2 open0 closed)

User story #4188: Add granular check on change request change (not on directive parameter)NewActions
User story #4189: Add granular check of directive parameter on change request mergeNewActions
Actions

Also available in: Atom PDF