I would like to try an accomplish two things.
There are great tutorials to help a novice like me in the subtask/parent relationshitp, but due to subtasks not being able to be used in Sprint planning I'd like to use standard issue types and have then update the epic they are associated with, using post functions in the workflow.
Hello Silviu,
I am in trouble to resolve the linked issue parent-child structure auto transition please help me how do i resolve this problem
My SIL post function :-
string sk;
bool alldesign = true;
for (sk in linkedIssues(parent)) {
if (%sk%.status != "Design Completed" && sk != key) {
alldesign = false;
}
}
if(alldesign) {
autotransition(3, parent);
}
I have two different issue types in one project where isuue type "Story Task" is parent and issue type "Task" as child i put the post fuction in Transition of child workflow issue type "Task"
But its not changing the transition of issue type "Story Task"
please help me how do i resolve this problem.
Hi Brian,
I'm guessing that you have used the parent predefined variable to do that from subtask to parent. You can get the CF value from another issue by using the issue key and the CF name/id, like this:
number val = DEMO-1.SomeNumericCF; // get the value
The rest of your task should be simple using this hint. You can find more information about variable resolution here, it's a valuable resource for novices, you will learn how to get and set CF values in seconds:
http://confluence.kepler-rominfo.com/display/SIL30/Variable+Resolution
If you need additional guidance, simply comment on my answer or send us an email, we're eager to help.
Happy SIL coding!
Silviu
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.