Environment field - Auto Assigning to the test cycle.

[asadiq]

Usually, QA is required to run the same test cases on Environment A and Environment (SIT and UAT).  We usually add one test cycle and clone it which means we also need to update the Environment field.

If we clone the test cycle before execution on SIT, in this case we have to manually fill out the Environment field. 

If we copy the test cycle once we have executed the test cycle on SIT (which contains the Environment field filled out with SIT) then we need to update the Environment field and change it to the current Environment (UAT).

Is there any way to bulk edit / assign the "Environment" field?

[Vishal Biyani · Accepted solution]

@asadiq 

• Is Test Cycle an issuetype in JIRA?
• Is there any field to identify if the issue is for Environment A or SIT?

You surely can bulk update the issues and update the Environment field.

Also, if there is a custom field that can help identify which Environment the issue is for, then Environment field can be updated during transition also

[asadiq]

Hi Vishal

Many thanks for your reply.

• Is Test Cycle an issuetype in JIRA?  No
• Is there any field to identify if the issue is for Environment A or SIT? Yes, Environment field