You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Thank you!
Hi @Gama, Márcio and welcome to the community,
Couldn´t reproduce the behaviour on my site (cloud) and cannot get a hint of a cause.
Did you check the "Activity" section within the TestRun? Any changes that were made in the issue should be logged there (like the history of issues). Maybe this gives a hint who, what or why the assignee was changed. Maybe we get a first information to further investigate any causing issue.
Best
Stefan
Thank you for your feedback @Stefan Salzl
Unfortunately the Activity section does not provide any additional information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok that seems really strange. Is it completly empty? it doesn´t even tracks that there has been a re-assignment?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It just logs the change in the assignee of the Test Execution and not the change in the assignee of the Test Runs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a bit missleading. The activity in the TestRun says "the assignee of THIS test execution" --> which means the test run. I just tested this in my instance (see screenshot).
Could you please also provide screenshots for better understanding?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was a solution ever found for this?
I am running into a similar problem. I cloned a Test Execution with 80 Tests associated to it. The cloned Test Execution inherited the Reporter and Assignee, as expected. However, the 80 Tests were changed from their respective TestRun Assignees to the Assignee of the Test Execution. There is no history in the Test Executions or Tests to indicate the change of TestRun Assignee and I have no idea, other than manually updating all 80 Tests, how to get the appropriate TestRun Assignee to carry over during the clone.Any ideas or solutions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @swilson
I would recommend to reach out to vendor support directly with this issue.
It seems this is more a technical question as I don´t know of any setting/configuration that would manipulate the testRunAssignee.
https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found when you assign an owner to the Test Execution, and view the test cases from that ID - it show all of the Assignee names as that name however, if you open up each Test Case, the Assignee is the actual name that had been assigned the Test Case. To me, this seems like a bug in the product. An unfortunate work around was to ask testers to refer to an external document tracking the Assignee and then execute in Xray. :-(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.