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

[docs] Document and refactor errata system integration, original #189 #15

atodorov opened this Issue May 26, 2017 · 0 comments


None yet
1 participant

atodorov commented May 26, 2017

Admin guide needs to say what an errata system is and how it is used in Nitrate
Also there is some messaging integration under tcms.integrations.errata which at least needs to be documented and enabled only if setting is configured
NOTE: except the integration this errata info is used only to produce a clickable link which really feels the same as attaching a bug tracker URL to the test run. Given the proposed changes in #185 I think we can refactor this template to actually use a Bug tracker link and its corresponding integrations.

atodorov added a commit that referenced this issue Jun 6, 2017

Remove integration with Errata System. Fixes #15
An Errata System is something which hasn't been documented since
the early days of this project and I guess is something internal
to Red Hat. This commit removes references to this system and also
removes the tcms.integrations.errata application together with its
messaging layer. If need be messaging can be brought back together
and refactored to be more versatile.

- removed configuration setting ERRATA_URL_PREFIX
- adds migrations/

@atodorov atodorov closed this in f36b761 Jun 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment