| Summary: | [RFE] possibility to enforce tester to fill in environment variables | ||
|---|---|---|---|
| Product: | [Other] TCMS | Reporter: | Tomas Pelka <tpelka> |
| Component: | Application | Assignee: | Yuguang Wang <yuwang> |
| Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | azelinka, ctang, junzhang, llim, nli, pvine, vchen, yawli |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-22 06:36:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 593666 | ||
|
Description
Tomas Pelka
2011-06-22 11:48:54 UTC
A possible initial use case for this feature might be something like this. As a user of TCMS I would like to be able to set default and possibly required environment selections that would be used for all runs created from that plan. The environment fields could be defined to either be required or optional but would appear as the run is started. Required fields would require a non empty selection before any run results could be saved. The selection of required or optional made at the plan level could be for all environments fields for the plan. Worth discussion is the possibility to select individual environment fields for optional or required rather than all or none. it seems a special function for your team and your work flow, it will confuse others. and now many user complained tcms is too big to use. So we should avoid to add special functions into TCMS. |