Bug 1288849
| Summary: | No docs\examples on regex option for flag groups. | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Yaniv Lavi <ylavi> |
| Component: | Extensions | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Extensions sub component: | RuleEngine | QA Contact: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | jfearn |
| Version: | 4.4 | ||
| Target Milestone: | 5.0-RH15 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.0.4-rh48 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-09 00:10:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yaniv Lavi
2015-12-06 13:57:15 UTC
How does a docs bug get pushed so far to the future? I want to be able to use the features now, can you at least provide the info here, so I can start using it. It's a perl regex. The format is the same as you would use in a bug search in the "Matches Regular Expression" If you make a bug search using the Custom Search "Flags" "matches regular expression" <regex here> You can experiment with what will be matched. If you give some detail on what you want to do, I can probably provide some examples. This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. |