diff options
| author | Niedermann IT-Dienstleistungen <stefan-niedermann@users.noreply.github.com> | 2022-02-18 10:48:17 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-18 10:48:17 +0300 |
| commit | 6b3479752bca1a1bae33edbf5ca58c9e7bc3f213 (patch) | |
| tree | e74cd42f24c2f2664c4cab6ecdc7538b02e57619 /FAQ.md | |
| parent | 72b03d11f45e12e793a5d02a5ff3d34028e32104 (diff) | |
Add Upcoming Analyzer to FAQ
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -2,6 +2,7 @@ - [I have experienced an error](#i-have-experienced-an-error) - [Why has my bug report been closed?](#why-has-my-bug-report-been-closed) +- [Why is my card not visible in the upcoming cards view?](#why-is-my-card-not-visible-in-the-upcoming-cards-view) - [Why don't you make an option for…?](#why-dont-you-make-an-option-for) - [Why don't you make an iOS app?](#why-dont-you-make-an-ios-app) - [How to receive notifications when a due date is reached?](#how-to-receive-notifications-when-a-due-date-is-reached) @@ -60,6 +61,10 @@ This is necessary for two reasons: 1. We have a rapid development cycle - bugs which have been reported weeks ago might no longer relevant 2. We are loosing the context of a report or a question over the time. We have many things to care about and digging into an issue deep and then relying on an response which is not coming is a waste of our limited free time +## Why is my card not visible in the upcoming cards view? + +Checkout the [Upcoming Analyzer](https://upcoming-analyzer.niedermann.it/) to check out the criterias your card needs to match to be shown in the upcoming cards view. + ## Why don't you make an option for…? We prefer good defaults over providing an option for each edge case. Our resources are quite limited, so we have to consider introducing new options very carefully. |