Cloning an Xray Test Execution Changed TestRun Assignee of all Tests to Test Execution Assignee

Question

I have little to no experience with Xray so I cannot figure out why this happened...

Test Team clones a Test Execution.  The expect the Reporter, Assignee, and all TestRun Assignees to copy over from the original Test Execution ticket.

I did verify Modify Reporter and Assignable User Permissions in the Project Permissions.

When reviewing the cloned Test Execution ticket, the Reporter & Assignee are fine.  BUT, when reviewing the Tests, all 80 of them now have the Assignee of the Test Execution ticket instead of the individual assignees previously set on the original ticket.

What am I missing?

Sue Wilson · Answer

@Tammy Fister , according to Xray Support, this is working as designed.  :-(

You could submit a Problem Report, Other, or Feedback ticket directly to Xray Support. Not sure they will change it, but I don't see a way to search their support platform to upvote any existing tickets with this same problem.

Xray Support:  https://jira.getxray.app/servicedesk/customer/portal/2

You have to log in and, in some cases, provide a valid SEN.

Tammy Fister · Answer

Where do we vote to get this fixed? It is very time consuming.

Sue Wilson · Answer

Hi @David W , I reached out directly to Xray support and this is the answer they provided.  Not what we were hoping for, but it is a definitive answer to what we see. I hope this helps.

"Thank you very much for using Xray Cloud and for contacting the Support Desk.

As explained on the following documentation link, when cloning a Test Execution issue, all the Test issue associations will also be cloned. However, a new Test Run is created for each Test so that the new Test Execution issue has no execution state.TestExecution-Clone

So, a new Test Run will be created, and when it´s created, it will retrieve the Assignee and Reporter fields from the cloned Test Execution that got those fields from the original Test Execution.

Regarding the Assignee field, you can, before cloning the Test Execution, change it to Unassigned so that when cloning the Test Execution, the Assignee field will be as Unassigned, and you´ll just need to put that Assignee back on the original Test Execution.

Regarding the Reporter field, the cloned Test Run will always get the Reporter field from the associated Test issue.

This is the expected behavior of the Assignee and Reporter fields."