[#JRA-8387] Bulk Open - Atlassian JIRA

JIRA

Bulk Open

Created: 01/Nov/05 03:05 PM Updated: 01/Nov/05 05:36 PM

Component/s:

Bulk Operations

Affects Version/s:

3.3.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

~~JRA-2427~~ Bulk Workflow Transition

Participants:	=Neal Applebaum, Bernard Durfee and Mark Chaimungkalanont [Atlassian]
Since last comment:	2 years, 42 weeks, 6 days ago
Labels:

Description

« Hide

I had a bunch of issues in a component that I wanted to version. So I needed to move them to a new project for just that component. The bulk move worked fine, but the bulk edit to change the version would not work because a good number of the issues were closed. The bulk operations should be able to bulk edit the status or bulk edit the version information, even when the issues are closed.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 01/Nov/05 04:06 PM

I can think of 2 workarounds you could try:
1) Change the workflow of the project to one which allows edit of closed issues - a bit of work with some downsides. You need to copy the existing workflow, then edit the copy to allow for editing of closed issues (http://confluence.atlassian.com/x/TtoB), then migrate the project and all its issues to the new workflow.
2) Delete the version and re-add it.
Note that when you delete a version from a project, it'll ask you to re-assign the issues assigned to that version to another version .. regardless of the issue status - allowing you to edit closed issues even if the workflow doesn't allow it. See http://jira.atlassian.com/browse/JRA-8166 where Atlassian confirmed this backdoor is intentional.
So, you could create version "V-NEW" and then delete version "V-OLD". When deleting version "V-OLD" tell it to move all issues (it'll move closed ones too) to "V-NEW". Then just rename "V-NEW" to "V-OLD". Voila - you've outsmarted JIRA (no offence intended). See this discussed at
http://forums.atlassian.com/thread.jspa?messageID=257220724&#257220724

Obviously you would test this out on a test system first.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 01/Nov/05 05:36 PM

Neal is spot on with this. The first way which adds jira.issue.editable to your workflow is probably the most best way to go if you want to be able to edit closed issues.

Bulk progress workflow is being pencilled in as a highly likely 3.5 feature, so we shouldn't have this issue in the system much longer