Community
Participate
Working Groups
It would be great if the Bugzilla editor had an action to create subtasks similar to the JIRA editor. The created bug would have the "Depends On" attribute preset to the parent task and could also inherit other attribute values.
Maybe just add this to the CloneTaskAction (now it only sets a comment with back link url) or in a more extensive implementation in the bugzilla task, See latest patch in bug 161646: [patch] Support for Clone this bug. It contains a stub in NewBugzillaTaskEditor to handle setting more fields, if it recognizes them.
Is there any way that we could make this something that is extensible? I see that Jira already contributes this type of action and it would be nice to have api for it so that developers do not have to copy this action for each connector.
Yes, I would definitely like this to be a common action. The driver for generalizing it can be Bugzilla, which to start could just copy the right components. Shawn: if this doesn't make it high enough Steffen's priority list consider submitting a patch.
(In reply to comment #0) > It would be great if the Bugzilla editor had an action to create subtasks > similar to the JIRA editor. The created bug would have the "Depends On" > attribute preset to the parent task and could also inherit other attribute > values. Stefen, should I look at this? If so, what other attributes did you have in mind?
Sounds great, Frank. Take a look at JiraTaskDataHandler.initializeSubTaskData() and the corresponding action in JIRA. For Bugzilla this should work the same way, a single click action to open the editor for creating a sub-task. The Blocks attribute should be set to the parent task, not the Depends On attribute as the descriptions suggests. You can use the AbstractTaskDataHandler.cloneTaskData() method for copying other attributes. I haven't done that for JIRA, yet, but it should be straight forward.
(In reply to comment #5) > Sounds great, Frank. Take a look at JiraTaskDataHandler.initializeSubTaskData() > and the corresponding action in JIRA. For Bugzilla this should work the same > way, a single click action to open the editor for creating a sub-task. The > Blocks attribute should be set to the parent task, not the Depends On attribute > as the descriptions suggests. I looked at this and have a Question. Should I move NewSubTaskAction from org.eclipse.mylyn.internal.jira.ui.actions to org.eclipse.mylyn.internal.task.ui.actions or should I create an Bugzilla specific Action. > > You can use the AbstractTaskDataHandler.cloneTaskData() method for copying other > attributes. I haven't done that for JIRA, yet, but it should be straight > forward. My implementation use AbstractTaskDataHandler.cloneTaskData so Summery and Description get set from the parent. Is this OK. When I get the answer I will post soon an Patch.
(In reply to comment #6) > Should I move NewSubTaskAction from org.eclipse.mylyn.internal.jira.ui.actions > to org.eclipse.mylyn.internal.task.ui.actions or should I create an Bugzilla > specific Action. It is okay to duplicate the action code for now. We can generalize later on. > My implementation use AbstractTaskDataHandler.cloneTaskData so Summery and > Description get set from the parent. Is this OK. It seems that this does make much sense for a subtasks as it will a specific summary and description to that task. How about reseting these to empty strings after cloning?
Created attachment 83352 [details] patch Please copy file org.eclipse.mylyn.jira.ui/icons/etool16/sub-task-new.gif to org.eclipse.mylyn.bugzilla.ui/icons/etool16/sub-task-new.gif to get this patch work.
Created attachment 83353 [details] mylyn/context/zip
Thanks Frank! Patch looks great to me. The only minor thing that should be changed is the label for the action, it should be "Subtask". Rob, assigning to you for reviews, since the patch touches Bugzilla code.
Awesome Frank. Patch applied and ip log updated. Updated action label to 'Subtask' as Steffen suggested and added your name to the Javadoc of NewBugzillaSubTaskAction (convention whenever adding a new class to the code base).
Marking resolved.
