For example, we have an 'awaiting build' and 'awaiting deployment' workflow step, it would be good if we could bulk transfer everything in these to the next step in the workflow.

http://www.atlassian.com/software/jira/docs/latest/jelly.html#TransitionWorkflow

This much support for an issue and its not even scheduled yet?

This script assumes you only have the one window open in safari (told you it was brittle). Do a search in Jira to list all of the issues you want to close. click on the first issue to get it's detail screen, then run this script. It will loop through all the issues in the search closing them all, and eventually hanging when there aren't any more - just click stop in your script editor to stop it when it's done (told you it was brittle).

activate application "Safari"
tell application "System Events"
tell process "Safari"
repeat
repeat with wait from 0 to 500000
end repeat
set done to false
repeat while not done
try
click static text "Close Issue" of UI element "Close Issue" of group 36 of UI element 1 of scroll area 1 of group 4 of window 1
set done to true
end try
end repeat
repeat while the title of window 1 does not start with "Close issue"
end repeat
repeat with wait from 0 to 100000
end repeat
set done to false
repeat while not done
try
click button "Close Issue" of group 44 of UI element 1 of scroll area 1 of group 4 of window 1
set done to true
end try
end repeat
repeat while the title of window 1 does not start with "[#"
end repeat
repeat with wait from 0 to 100000
end repeat
set done to false
repeat while not done
try
click static text "Next >>" of UI element "Next >>" of group 54 of UI element 1 of scroll area 1 of group 4 of window 1
set done to true
end try
end repeat
end repeat
end tell

end tell

http://jira.atlassian.com/browse/JRA?report=com.atlassian.jira.plugin.system.project:popularissues-panel

If you are going to do it through SQL, please take into consideration the OS Workflow steps, current and history. These tables are described in the entitymodel.xml file.

Also, as of 3.3 you can now transition issues through the SOAP interface.

Cheers,
Nick

This feature is being currently implemented and has been scheduled for inclusion in the next major release - JIRA 3.5 - but as yet, the 3.5 release date has not been finalized. A very tenative date for the 3.5 release is Feburary 2006 - although we may try to release earlier with this feature included.

Regards,
Keith

I don't understand what's so hard about writing an SQL query. It doesn't matter if it takes the server an hour, you're denying the users the ability to make that choice given the implications.

We're in the middle of upgrading 2.6.1 to 3.1, so I doubt we will upgrade to 3.5 this year, but its good to know this issue is being resolved. Thanks for the work around, but unfortunately, I don't believe my boss would go for it.

Does the bulk transition allow disabling notifications from being sent when the bulk transition is being done? This is a fairly important feature since I know many, many users will use this feature to change thousands of issues and hence cause massive amounts of "spam" being sent out from Jira. From end-user acceptance point of view, being able to disable the messages from being sent would be very good.

The bulk workflow transition does not currently allow notifications to be disabled during execution.

This issue is being tracked at JRA-2732, while another option to send only one email for bulk edits is being discussed at JRA-4303.

A temporary workaround would also be to disable mail notifications during the operation of the bulk change:

http://www.atlassian.com/software/jira/docs/v3.4.2/restore_data.html#Disabling+email+sending%2Freceiving

requiring JIRA to be stopped and started before and after the bulk change.

Regards,
Keith