Apache Allura™

• Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,3 @@
 As a follow-up to [#4339], I know some projects would appreciate the ability to bulk move tickets. In some cases, the purpose of moving tickets in the first place is so the projects can consolidate multiple ticket tools (eg., if they had multiple trackers migrated).
+
+Also, we need to make sure not to spam users with a ton of notifications when the bulk moves are done. Probably related to [#2502]

Originally by: wohler

The purpose you state was our need. When we switched from SourceForge 1.0 to 2.0, we decided to retire the legacy Feature Requests, Patches, and Support categories and consolidate them into a single Tickets tool.

A second purpose would be to change the name of the mount point. We would like to rename "bugs" to "tickets."

And yes, please implement [#2502] at the same time.

Thanks!

• labels: support, p3 --> support, p3, 42cc
• milestone: limbo --> forge-backlog

• status: open --> in-progress

Created #301: [#5656] Bulk move tickets (4cp)

Closed #301. je/42cc_5656

• status: in-progress --> code-review

• QA: Tim Van Steenburgh
• Milestone: forge-backlog --> forge-may-17

• QA: Tim Van Steenburgh --> nobody

• QA: Dave Brondsema

• status: code-review --> in-progress
• Milestone: forge-may-17 --> forge-backlog

Works well, but room for improvement:

• new files need the Apache license header, looks like you got that for one but not mass_move.html but not mass_move_report.html
• can the core logic in move_tickets be moved out of the controller and into the model somewhere? Or a helper function, if model isn't suitable.
• I haven't tested it, but I suspect with a mass edit of hundreds of tickets would take a while to run and could timeout. If so, then this should be run as a background task. The refactoring from previous bullet point will make that easier to do.
• the To: 501bf32707b25c0ed09d92a9 email header isn't very great
• instead of creating a new jinja2.Environment you should be able to use g.jinja2_env which is already set up
• In the email notification, [testall:moar] doesn't render as a link, so I guess it'd be better not to have the brackets. Neither do individual ticket references like [movetix:tickets:#6] which seems broken - maybe because the ticket is currently in transition and so it's not indexed. Maybe best to not link those either, in that case?

Created #353: [#5656] Followup to bulk move tickets (3cp)

• status: in-progress --> code-review

Closed #353. je/42cc_5656

• status: code-review --> in-progress

• The move_tickets task should be in ForgeTracker, not in Allura.
• minor syntax formatting: lines 264-266 of ForgeTracker/forgetracker/model/ticket.py should be indented
• can the task send a flash notification of completion to the user who did the changes? Then you'll know it's done next time you load a page, without having to check your email. M.Notification.post_user is the function to use for that.
• [#6219] (just merged to master today) added new TicketMonitoringType values. Can you rebase and add those into the TicketMonitoringType checks here too?

Created #358: [#5656] Followup to bulk move tickets (1cp)

• status: in-progress --> code-review

Closed #358. je/42cc_5656 (forced update)

• status: code-review --> closed
• Milestone: forge-backlog --> forge-may-31