Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#6365 closed task (implemented)

Use keywords like SponsorG20120930 for sponsor deliverables instead of milestones

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Internal Services/Service - trac Version:
Severity: Keywords:
Cc: mikeperry, nickm, arma, phobos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We're currently using Trac's milestone field for two things: version milestone and sponsor milestone. It would be good to assign a ticket to both a version like Tor 0.2.4.x-final and to a sponsor milestone like Sponsor G, September 30, 2012. Mike and Nick suggested to use Trac keywords for this purpose.

Two questions:

  • Is SponsorG20120930 a good format for such keywords?
  • Is there an easy way to modify existing tickets in bulk? I don't mind so much doing it manually, but it's going to generate a lot of emails.

Child Tickets

Change History (9)

comment:1 in reply to:  description Changed 7 years ago by arma

Replying to karsten:

Mike and Nick suggested to use Trac keywords for this purpose.

Sounds great to me.

comment:2 Changed 7 years ago by karsten

Oh, and sponsor Z keywords wouldn't have a date, so it'd be just SponsorZ.

comment:3 Changed 7 years ago by karsten

Milestone: Sponsor Z: November 1, 2013

Assigning to milestone Sponsor Z: November 1, 2013 as a test for using Trac's Batch Modify feature. Not sending an email notification for this one.

comment:4 Changed 7 years ago by karsten

Keywords: easy added

Oh, and to make the test even better, adding a keyword that will hopefully survive the next Batch Modify operation. Again, not sending out an email notification for this one.

comment:5 Changed 7 years ago by karsten

Keywords: SponsorZ added
Milestone: Sponsor Z: November 1, 2013

And now, (hopefully) removing the milestone and adding a keyword. If this works as expected, we're all good for modifying tickets in bulk as sketched out in this ticket. Again, no email notification.

comment:6 Changed 7 years ago by karsten

Keywords: SponsorZ20131101 added; SponsorZ removed

Last test for today. Trying to remove keyword SponsorZ and picking keyword SponsorZ20131101 instead. That's -SponsorZ SponsorZ20131101 in Trac's Batch Modify line for keywords. Just in case we change our minds about keyword formats we'll want to do a bulk operation like this. Aaand, not sending an email notification.

comment:7 Changed 7 years ago by karsten

Keywords: easy SponsorZ20131101 removed
Owner: changed from erinn to karsten
Status: newassigned

So, I'm all set for changing existing tickets using Trac's Batch Modify plugin. See the tests above. I'll do the bulk change as suggested in the description above, again without sending out notification emails for every single change.

Oh, and removing the keywords which were only there for testing purposes.

comment:8 Changed 7 years ago by karsten

Resolution: implemented
Status: assignedclosed

Changed all tickets that were assigned to sponsor milestones and deleted the milestones. Closing.

comment:9 Changed 4 years ago by qbi

Component: TracService - trac

Move all tickets from trac to "Service - trac" component.

Note: See TracTickets for help on using tickets.