Issue Details (XML | Word | Printable)

Key: JRA-13456
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Eric Dalquist
Votes: 6
Watchers: 5
Operations

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

Bulk add to Affects Version/s

Created: 31/Aug/07 11:42 AM   Updated: 30/Jan/08 10:18 AM
Component/s: Bulk Operations, Issue Fields
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Part
 
Reference
 

Participants: Eric Dalquist, Kief Morris and Patrick Berry
Since last comment: 1 year, 5 days ago
Labels:


 Description  « Hide
Add an option to Bulk Add to the Affects Version/s field. The current bulk operation will replace the existing selected versions with the version selected in the bulk operation.

Example use case:

Issue A affects versions 1.1, 1.2 and 1.3
Issue B affects versions 1.2 and 1.3

I release version 1.4 which doesn't fix either issue and want to add version 1.4 to the affects field of both issues. I cannot use the Bulk Change Affects Version/s since it would simply set the field to just 1.4 for both issues.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Patrick Berry added a comment - 03/Oct/07 11:15 AM
How are people currently working around this, other than editing issues individually?

Kief Morris added a comment - 03/Oct/07 11:32 AM
I have a half-assed system of getting a list of unresolved issues affecting the previous version, sorting it by "affected version/s", and then selectively bulk editing them in batches which have the same set of affected versions. For example, first I change everything that affects versions 1.0, 1.1, 1.2, 2.0, and 2.1. Then I change everything that affects 1.1, 1.2, 2.0, and 2.1. Then ....

It involves painstakingly going through the "bulk edit" page and ticking those issues that fall into the current batch. Sorting first makes this a bit easier.

But it's still very, very painful.