[DOCS-10972] Add a link to Free Tier limitations in the Command Limitations section Created: 02/Nov/17 Updated: 11/Sep/18 Resolved: 02/Nov/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Chris Cunningham | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 15 weeks ago | ||||
| Epic Link: | DOCSP-2982 | ||||
| Story Points: | 0.1 | ||||
| Description |
|
A customer raised a support ticket as they were not able to use $where after upgrading from an M0 => M2. When they looked at the Command Limitations in Free Tier Clusters section of the MongoDB Atlas documentation, they were not clear that an M2 had the same limitations as an M0. Perhaps a link back to the Atlas M0 (Free Tier), M2, and M5 Limitations section of the documentation in the first sentence would make this more obvious to the user. |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 02/Nov/17 ] |
|
Merged and Published, Thanks for the heads up on this! |