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

[DEMO] Environment cannot be set for test plan #73

Closed
okainov opened this Issue Oct 26, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@okainov
Contributor

okainov commented Oct 26, 2017

Description of problem

Cannot use environment groups

Component (web, API, etc)

Web

Version or commit hash (if applicable)

Demo https://demo.kiwitcms.org

How often reproducible

Always

Steps to Reproduce

  1. Create some env properties
  2. Create some env group
  3. Go to "New test plan"
  4. Make sure environment groups combobox exists, select env group
  5. Press "Create"
  6. Press "Edit"
  7. Make sure combobox value is "-----", no env group was actually set.

Actual results

Combobox value is "-----", no env group was actually set.

Expected results

Env group should be set

Looks like regression since in Nitrate it was fine. Or maybe DEMO issue, I haven't checked it with real instance

@atodorov

This comment has been minimized.

Show comment
Hide comment
@atodorov

atodorov Oct 27, 2017

Member

Thanks for the bug report. I was able to reproduce. This also looks like a permissions issue. Will look further into it.

Member

atodorov commented Oct 27, 2017

Thanks for the bug report. I was able to reproduce. This also looks like a permissions issue. Will look further into it.

atodorov added a commit that referenced this issue Oct 27, 2017

@atodorov atodorov closed this in #83 Oct 27, 2017

atodorov added a commit that referenced this issue Oct 27, 2017

@atodorov

This comment has been minimized.

Show comment
Hide comment
@atodorov

atodorov Oct 27, 2017

Member

@GodfatherThe this and #74 have been fixed, thanks for spotting the problems. I will update the demo in a few days. Note: when you see a changelog update on GitHub that means the demo has been updated.

Member

atodorov commented Oct 27, 2017

@GodfatherThe this and #74 have been fixed, thanks for spotting the problems. I will update the demo in a few days. Note: when you see a changelog update on GitHub that means the demo has been updated.

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