I'm hoping someone can help me with this as i have no idea how to code. I have a project that creates multiple subtasks and tickets in other projects throughout the workflow. I need to find a way to update all subtask and linked tickets based on updates to the parent ticket and vice a versa. Is this even possible.
Hi Bob,
Yup i have that plugin and am trying to work with it. It should be a relatively simple setup but for whatever reason the information is not rolling back up to the parent from the subtask.
With that being said when i want to update the subtask this project has roughly 12 different subtask types. do i need to create an new post function for each issuetype in the transition when i want to update all of the linked issues in the parent?
Not necessarily. If the same update applies to multiple issues, then one post function using a JQL query that returns the right list of issues to be updated should work. See https://bobswift.atlassian.net/wiki/display/CW/How+to+use+JQL+to+find+issues+to+update. If things aren't working as expected, look in the JIRA application log for error messages. See https://bobswift.atlassian.net/wiki/display/CW/How+to+get+problem+determination+information for more information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
all of the issues that this parent ticket would need to update are issuetype in (Sub-task, "OPR Subtask Type 1","OPR Subtask Type 2","OPR Subtask Type 3","Status Update Sub-Task", "New Hire Profile","New Hire Profile-Philadelphia Only", "TPO Sub-Task 2","TPO Sub-Task 3","TPO Sub-Task 4","IT New Hire Setup (HR USE ONLY)", "Facilities Task") So i would enter that into the "jql query" field and then what would i do to ensure that it only updates those issue types that are linked to or are subtasks of that particular issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
parent = %original_key% and issuetype in ... should do it. Run an example in the JIRA UI with a specific key and verify it is syntactically correct JQL and returns the right issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bob. I ran parent = (specific key) and issuetype in (Sub-task, "OPR Subtask Type 1","OPR Subtask Type 2","OPR Subtask Type 3","Status Update Sub-Task", "New Hire Profile","New Hire Profile-Philadelphia Only", "TPO Sub-Task 2","TPO Sub-Task 3","TPO Sub-Task 4","IT New Hire Setup (HR USE ONLY)", "Facilities Task") as suggested and it returned what it should. Then I added the transition Issues to update: %original_key% JQL query: parent = %original_key% and issuetype in (Sub-task, "OPR Subtask Type 1","OPR Subtask Type 2","OPR Subtask Type 3","Status Update Sub-Task", "New Hire Profile","New Hire Profile-Philadelphia Only", "TPO Sub-Task 2","TPO Sub-Task 3","TPO Sub-Task 4","IT New Hire Setup (HR USE ONLY)", "Facilities Task") And still no updates to any subtasks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The "Issues to update" needs to be the results from the JQL query. That would be %jql_result_list%. The reference is: https://bobswift.atlassian.net/wiki/display/CW/Substitution+variables.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yup that makes sense. Made that change to now read Issues to update: %jql_results_list% JQL query: parent = %original_key% and issuetype in (Sub-task, "OPR Subtask Type 1","OPR Subtask Type 2","OPR Subtask Type 3","Status Update Sub-Task", "New Hire Profile","New Hire Profile-Philadelphia Only", "TPO Sub-Task 2","TPO Sub-Task 3","TPO Sub-Task 4","IT New Hire Setup (HR USE ONLY)", "Facilities Task") Still nothing. Sorry i'm a bit slow with picking this up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the updates need to be done as part of the workflow, then Update on Transition for JIRA has the Update issues post function that can be used to update various other issues using Substitution variables.
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.