Bug 1288846
| Summary: | Allow to set needinfo on assignee\reporter\qa contact\docs contact | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Yaniv Lavi <ylavi> |
| Component: | Extensions | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Extensions sub component: | RuleEngine | QA Contact: | Rony Gong 🔥 <qgong> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | medium | ||
| Priority: | low | CC: | blc |
| Version: | 4.4 | ||
| Target Milestone: | 5.0-RH4 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.0.4-rh18 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-03 00:25:29 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:52:28 UTC
The severity for our flows is high, why did you change this? Note that needinfo for assignee and qa roles are settable from the need info box below the new comment box. You can use it even if you aren't making a comment. (In reply to Jeff Fearn from comment #3) > Note that needinfo for assignee and qa roles are settable from the need info > box below the new comment box. You can use it even if you aren't making a > comment. This request is for the rules engine. *** Bug 1679762 has been marked as a duplicate of this bug. *** *** Bug 1687246 has been marked as a duplicate of this bug. *** Verified on QA server, PASS Now, in the rule action page, for the needinfo action. we can set it with %reporter%, %assignee%..... It can work well. This change has been deployed to partner bugzilla, please test and let us know if you have any issues. https://partner-bugzilla.redhat.com/ 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. |