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

Errata field visible when ERRATA_URL_PREFIX is empty string #186

Open
atodorov opened this Issue Apr 29, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@atodorov
Contributor

atodorov commented Apr 29, 2017

When editting a Test Run there is an Errata field visible even though the ERRATA_URL_PREFIX setting is an empty string. Also this isn't documented properly from what I can tell.

  1. The Errata edit field needs to be hidden if the setting is not configured
  2. In test run view template the field should be hidden if not visible
  3. Admin guide needs to say what an errata system is and how it is used in Nitrate
  4. Also there is some messaging integration under tcms.integrations.errata which at least needs to be documented

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. Also 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 to MrSenko/Nitrate that referenced this issue Apr 30, 2017

Hide Errata field if ERRATA_URL_PREFIX not set. Fix #186
Signed-off-by: Mr. Senko <atodorov@mrsenko.com>
@atodorov

This comment has been minimized.

Show comment
Hide comment
@atodorov

atodorov Apr 30, 2017

Contributor

3), 4) and NOTE moved to #189

Contributor

atodorov commented Apr 30, 2017

3), 4) and NOTE moved to #189

atodorov added a commit to MrSenko/Nitrate that referenced this issue May 24, 2017

Hide Errata field if ERRATA_URL_PREFIX not set. Fix #186
Signed-off-by: Mr. Senko <atodorov@mrsenko.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment