Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Visual Analytics |
| Version | 18.0 |
|
|
123 KB
|
342 KB
This behavior is OK but whether you have primary discrete year or secondary discrete year, the end user behavior is the same.
whether you have primary discrete year or secondary discrete year, the end user behavior is the same.
Question is why we have done this only for Year ? Why this was not done for other Date functions like Month Quarter ?
Also if end user behavior is same then what is the use of this feature ? Why don't we just give primary discrete only and not Secondary discrete ?
whether you have primary discrete year or secondary discrete year, the end user behavior is the same.
Question is why we have done this only for Year ? Why this was not done for other Date functions like Month Quarter ?
Also if end user behavior is same then what is the use of this feature ? Why don't we just give primary discrete only and not Secondary discrete ?
Question is why we have done this only for Year ? Why this was not done for other Date functions like Month Quarter ?
2 reasons:
-- functionally, the end user behavior is not the same between primary & secondary date groupings for Months, quarters, etc
-- There was a technical reason we did it this way. Asif & I had a discussion on it and b/c there was no adverse end user impact, it wasn't worth the dev cost to try & modify the behavior.
Also if end user behavior is same then what is the use of this feature ?
If you read my statement carefully, you'll see I mentioned it for "year" only. Its not true for any other date groupings. We have year in both for consistency as well as primary defaults to discrete while secondary defaults to continuous.
Question is why we have done this only for Year ? Why this was not done for other Date functions like Month Quarter ?
2 reasons:
-- functionally, the end user behavior is not the same between primary & secondary date groupings for Months, quarters, etc
-- There was a technical reason we did it this way. Asif & I had a discussion on it and b/c there was no adverse end user impact, it wasn't worth the dev cost to try & modify the behavior.
Also if end user behavior is same then what is the use of this feature ?
If you read my statement carefully, you'll see I mentioned it for "year" only. Its not true for any other date groupings. We have year in both for consistency as well as primary defaults to discrete while secondary defaults to continuous.
As per above discussion verified.
As per above discussion verified.
Issue #14200 |
| Closed |
| Won't Fix |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
This behavior is OK but whether you have primary discrete year or secondary discrete year, the end user behavior is the same.