I have some Issue types under which sub-task issue types are defined.
Now I need to customize the sub-task issue types based on the Issue types.
Please any one provide the clue for this.
Also if any plug-in exist for this please specify.
i hear you renjith. just was wondering if it might be possible cause i also had an solution like this with "Clone" function from inside "More Actions"
Thanks Renjith, this approach make me to enter the script every time I create an issue.
Instead, I tried to analyze the blocking some subtasks in core code, I found a class file which is SubTaskBlockingCondition.class
it's java code look as follow
public class SubTaskBlockingCondition extends AbstractJiraCondition
public boolean passesCondition(Map transientVars, Map args, PropertySet ps)
Issue issue = getIssue(transientVars);
SubTaskManager subTaskManager = ComponentManager.getInstance().getSubTaskManager();
Collection subTasks = issue.getSubTasks();
if ((subTaskManager.isSubTasksEnabled()) && (!subTasks.isEmpty()))
passCondition = false;
for (iterator = subTasks.iterator(); iterator.hasNext(); )
GenericValue subTask = (GenericValue)iterator.next();
String statuses = (String)args.get("statuses");
StringTokenizer st = new StringTokenizer(statuses, ",");
String statusId = st.nextToken();
passCondition = true;
passCondition = false;
Is my approach right and am I looking the exact requirement thing?
One of the ways to implement this feature is to have a "loopback" workflow transition called "Create Subtask" , basically on the post-function of this transition you can create the sub-task using script runner plugin, though this way is more verbose but it kind of works well as the end-user sees the button "Create Subtask" clicks on this and the sub-tasks of a certain type can be generated.
I have defined a number of sub-tasks in a project under different issue types.
I need to retrieve
only those sub-tasks for bug type if I select 'sub-task for Bug',
only sub-tasks for New Feature if I select 'sub-task for New Feature' and soon.
How this is possible?
If I understand this correctly, you want to restrict the available sub-tasks based on the issue type of the parent? For example, under "bugs" you only want to allow the sub-tasks of "feature" and "test", although your sub-task list is feature, test and action?
I'm trying to make a filter as follow
project = MyProject AND parent = MYP-1
--This implies in a project called MyProject, the subtasks are retrieved based on the parent key MYP-1(which is a bug type)--
Now I want to know Is there any method which returns a issue key when a issue type(bug) is given?
I'm still not quite understanding this.
I'm really not sure what filters have to do with the original question, but the answer to that is to use the "parent" function in JQL - see https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Parent . A filter for "parent = myp-1" will work. If you only want "bug" sub tasks, then add the clause "and issuetype = bug"
The requirement just changed as:
I defined a number of sub-tasks issue types in a project like subtask1,subtask2,...,subtask10;
When I try to create a subtask,
I need to display subtask1,subtask5 for Bug
I need to display subtask4,subtask5 for New Feature
i.e., let's consider bug type issue
then in More actions, I click create a sub-task for this?
then a window is displayed
and in it, I want to display only some sub-task issue types for bug type issue
How can this be achieved?
i think i've seen some question like this here before.
i believe the goal is to seperate the possibile sub-task issue-types depending on what the parent issue-type is.
am i right?
so lets check this scenario...maybe other will understand that one better
if your parent issue is a "Story" you only want to see "story task" as possible selection when you're creating a subtask
if your parent issue is a "Bug" you only want to see "bug task" as possible selection when you're creating a subtask
am i right so far?
well unfortunately that's not that easy..as you can read in the feature request i've posted above.
this is not a feature of jira and nobody knows if or when it will be integrated.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs