Having some issues creating Jira automation, looking for it to do the following on status transition from a Dev to QA status.
- Transition = Dev In Progress > QA Ready
- Assign Issue = Set Parent Story = Assigned user from "Test Execution" sub-task.
I have attempted configuring this multiple ways but I keep seeing story set to "Unassigned".
1. Have attempted created both a Smart Value & Lookup Table using "Child" branch. Then referencing this {{Issue.assignee.accountID}} value in main branch.
2. Using JQL query to reference sub-tasks and Test Execution Summary, but can't seem to get this context correct to return only the specific story sub-task.
Hello @Ryan Chantelois
I'm not sure I'm clear on your scenario.
Which issue is being transitioned, the child issue or the parent issue?
If it is the child issue that is being transitioned, is there only one child issue that you want to be considered out of possibly multiple child issues? If you want to consider only one of the child issues for this rule, how do you distinguish that one child to make it unique from the other child issues? Does it have a different issue type, or keywords in the Summary?
Can you show us the rule(s) you have attempted, and tell us how each has not done what you expected?
Hi Trudy,
Story is being transitioned from a Development to QA status.
I need the story assignment to reflect the assignee of a "Test Execution" sub-task.
- There are a few child sub-tasks for development and QA.
- Currently I tried to distinguish based off of Summary Title and create a smart object to populate the assignee.
- Oddly enough this seems to work most of the time in our sandbox, but in production instance, it often sets story to unassigned.
Here's its configuration in sandbox.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
This is pretty easy pls see attached image as long as Assignee is on the Edit screen of Story and Test Execution is the parent of Story, you can do it as attached. Choose fields to set is the Assignee field -
Kind regards,
Mo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Moses, this is not the scenario, I need assignee to be set based on a child sub-task for "Test Execution".
I included a screenshot of my sandbox setup in another comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.