Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
Within project -> Filter by name (with regular expression) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO).
Workaround: add catching '^MR-\d+$' to the regex, e. g. '^(develop|master|MR).*'
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Within project -> Filter by name (with regular expression) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO). Workaround: add catching '^MR-\d+$' to the regex, e. g. '^(develop|master|MR).*' |
Within project -> Filter by name (with regular expression) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO). Workaround: add catching '^MR\-\\d+$' to the regex, e. g. '^(develop|master|MR).*' |
| Description |
Within project -> Filter by name (with regular expression) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO). Workaround: add catching '^MR\-\\d+$' to the regex, e. g. '^(develop|master|MR).*' |
Within project -> Filter by name (with regular expression) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO). Workaround: add catching '\^MR-\d+$' to the regex, e. g. '^(develop|master|MR).*' |
| Assignee | Parichay Barpanda [ baymac ] | Rick [ surenpi ] |