Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility to set a new pattern from the report #473

Open
radeklawgmin opened this issue Jan 29, 2019 · 0 comments
Open

Possibility to set a new pattern from the report #473

radeklawgmin opened this issue Jan 29, 2019 · 0 comments
Assignees
Labels
enhancement report size small Quick fixes and minimal-effort issues

Comments

@radeklawgmin
Copy link
Contributor

radeklawgmin commented Jan 29, 2019

From time to time there is a problem with patterns. Some of them are removed (not to say 'mysteriously deleted') from the DB and no matter how many times a given suite is re-run the user gets "Processing error".
The only solution to this problem is to remove such a record from the DB manually and re-run the suite.
It is a huge inconvenience when there is a problem with more than one missing pattern and the only solution is to remove corresponding records one by one from the DB.

It will be useful to have a possibility to set a new pattern from the report (there will be no need to log in to the DB, then look for the missing pattern and remove the record from the DB manually).
It will be nice if the user could decide whether and when such patterns will be set - otherwise it will be hard to figure out if a given pattern is the one that was approved by the user at some point in the past or it is a new pattern that was set automatically by the system because the previous pattern have been lost.
Note that the date when a given pattern has been set (this option is available currently) may say nothing to the user.

@waldemarGr waldemarGr self-assigned this Mar 4, 2019
@tMaxx tMaxx added the size small Quick fixes and minimal-effort issues label Sep 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement report size small Quick fixes and minimal-effort issues
Projects
None yet
Development

No branches or pull requests

3 participants