Just in time for JIRA 3.13 release (release notes), JIRA Issues Bucket plugin version 2.0 of this plugin is released as well (release notes).
This is a major productivity improvement. Some of the annoyances are taken care of now:
Filter out updated issues where the author of the last update is current user
In a typical way, when going through the bucket, I would open the issue in a new browser tab, so I would still have my bucket open and did not need to navigate back to it. That means that once the issue was actioned, I would go back and remove it from the bucket. However, because I just updated that issue, in few moments later the very same issue would re-appear in the bucket.
Not, anymore. You can select an option to exclude your updates from re-entering the bucket.
See BUCKET-21 for more information.
Issue view page operation that will allow for issue removal from a bucket
If you follow the process as described above, you will find it easier to remove the issue from the bucket directly on the view issue page. Once you are done, you can close that tab and refresh the page with the bucket. Done. No more looking to the “just actioned” issue in the list of issues in the bucket just so you can click the little trash icon.
See BUCKET-16 for more information.
This version uses new JIRA 3.13 API, therefore it won’t run on older versions of JIRA. Also, as JIRA drops support for Java 1.4 in the future major release (4.0), this plugin steps ahead and only supports Java 5.
See BUCKET-29 for more information.
As the dashboard pages are now shareable we had to make this feature work as well. So now, if you share the page with your bucket, other users will be able to see what’s in your bucket. Respecting the permissions, if you don’t own the bucket, you cannot do anything with it (read-only). And also you can only see the issues that you have permission to see. Keep in mind that as a result there could be more issues in the bucket than you can actually see.
See BUCKET-30 for more information.