Issue Details (XML | Word | Printable)

Key: JRA-9016
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Morten Kristiansen
Votes: 14
Watchers: 10
Operations

If you were logged in you would be able to see more operations.
JIRA

Bulk change subtasks

Created: 11/Jan/06 09:15 AM   Updated: 07/Aug/08 07:38 AM
Component/s: Bulk Operations
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Andy Armstrong, Gerald Innerwinkler, Ken Roland, Morten Kristiansen, Paul Csapo and Will Rau
Since last comment: 9 weeks, 3 days ago
Support reference count: 3
Labels:


 Description  « Hide
It would have been nice to be able to bulkchange subtasks when editing an Issue. F.ex. if I edit an issue and want to change Fix Version and Due Date, and my issue has 10 subtasks that I also want to change these fields in, it would be great to have a checkbox or something that says "Also change subtasks".

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andy Armstrong added a comment - 28/Aug/06 09:54 AM
We set up a workflow so that every new feature would get a standard set of subtasks (create design, implement feature, write test plan etc) but it was too painful to manage the subtasks this way. Some examples include:
  1. Moving a new feature to a different release meant manually moving all of the subtasks
  2. Resolving a feature meant first manually resolving all of the open subtasks
  3. Fixing the component on a new feature meant manually changing each subtask to use this feature

We have now decided to back away from subtasks and to use linked issues instead. This is actually more natural, as often the subtasks have already been reported as standalone issues. Now that we are switching away from subtasks, I'm finding it painful that there is no easy way to bulk delete subtasks too! So now I have to manually delete the eight subtasks for each of the tasks that we set up this way.

More than ever I'm of the opinion that subtasks were a mistake and that instead the linking mechanism should be beefed up to support the same functionality. So I'd like to see 'bulk change linked issues' as an equivalent tool to whatever is done here.


Will Rau added a comment - 09/Jul/07 05:22 PM
Has anyone seen or written a plugin to do this?

Gerald Innerwinkler added a comment - 14/Nov/07 09:54 AM
We are using subtasks in the same way as Andy reported. With the feature to change any already reported issue to be a subissue we like using subtasks to group things.
Subtasks also give the opportunity to easily do a more detailled feature-planning than using linked items without loosing the overview.

Paul Csapo added a comment - 22/Feb/08 06:31 AM
Hi Guys,
I like subtasks, but I tried a test with bulk changing them, and it lets me delete or edit multiple ones.

Which version have you tried this on? Recent version seems to support this.

regards,
Paul


Ken Roland added a comment - 22/Feb/08 07:07 AM
I think they mean a bulk change ability directly from the parent issue view.

I'm looking at this now too. We have some issues that have 20 or more subtasks. When you need to change just those sub tasks it can be a major hassle. The issue navigator has no easy way to "Find by Parent issue" to show only those 20 subtasks out of the hundreds.

I've implemented a listener now that updates subtasks on parent modification. So if certain fields are changed on the parent it automatically updates sub-tasks to the same. (Fix Version, Components, etc.)

What I'd like now is an "Edit" button in the sub-task list to save on the time to edit a sub-task. And a way to sort by Priority would be good ... I guess I'll be adding a lot now that I think about it.


Paul Csapo added a comment - 07/Aug/08 07:38 AM
Hi Ken, im very interested in how you set up your listener.
Are you able to share anything? :o)

I havent tried listeners yet, but one way which might help is to create a new custom field called "Parents Key", and to have this field visible on the subtasks issue type screen.
This way you can make the field mandatory, and whenever people create a subtask, thye just paste in the parent key, eg jira-9016.

Then you can set up a filter to show all items belonging to that parent key, and do a bulk change on them.
(also comes in handy in case someone moves the case by mistake, of it the subtask becomes un-associated with the parent by some means or corruption etc, so that you can easily identify which parent case need to sit under).

There might be a way for that value to be initially auto-populated upon creation, based on which case was the parent, but Im not sure yet.

regards,
Paul