Bug 872382 (PRODMGT-248)
| Summary: | Not possible to filter events by date and time range | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Charles Crouch <ccrouch> |
| Component: | Monitoring - Events | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | CLOSED EOL | QA Contact: | Mike Foley <mfoley> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | JON 3.1.1 | CC: | fbrychta, hbrock, hrupp, jshaughn, loleary, mithomps |
| Target Milestone: | --- | ||
| Target Release: | JON 4.0.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 856695 | Environment: | |
| Last Closed: | 2019-07-29 14:51:43 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 856695 | ||
| Bug Blocks: | |||
|
Description
Charles Crouch
2012-11-02 00:06:41 UTC
Created this bug to make sure we have a downstream issue corresponding to https://issues.jboss.org/browse/PRODMGT-248 targeting JON4.0 This worked perfectly for me. I don't find the time portion tricky at all. Click on the date you care about, update the time as needed. Worked. I think this is fine, setting ON_QA. The technical issues behind this are a decent looking time widget that can support i18n and the various time zones/display formats. This is further limited by Isomorphic recommendation that regular GWT components not be used with smartGWT. Relative time ranges would not be that difficult to add though like: 10m, 30m, 1h, 4h, 1d Given that it's doable today with the current widget, this won't make 3.3.0, Pushing to post-ga. JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121. This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version. |