#7510 Test extracting Allura tickets for Apache move


Re: http://mail-archives.apache.org/mod_mbox/allura-dev/201406.mbox/%3C53AC490E.2030100%40brondsema.net%3E

Do an export of tickets from SF Allura and write a script to go through the JSON and:

  • filter out all deleted & private tickets (except #6054)
  • change "QA" field to "Reviewer"
  • change "size" field to a labels like "sf-1", "sf-2", etc
  • change milestone:
    • to "backlog" if open/in-progress/validation/review/blocked
    • to "released" if closed/wontfix/invalild Or even better would to look at the git tags for releases 1.0.0, 1.0.1, and 1.1.0 and find the tickets that go into those, and assign milestones appropriately. Can default a ton of tickets to 1.0.0 and then smaller set for 1.0.1 and 1.1.0

Then import locally as a test run and see how it works.


Tickets: #7582


  • Dave Brondsema

    Dave Brondsema - 2014-07-11
    • Milestone: forge-jul-11 --> forge-jul-25
  • Dave Brondsema

    Dave Brondsema - 2014-07-11
    • Size: --> 2
    • status: open --> in-progress
    • assigned_to: Alexander Luberg
    • status: in-progress --> code-review
  • al/7510 in my fork

  • Dave Brondsema

    Dave Brondsema - 2014-07-15
    • status: code-review --> in-progress
  • Dave Brondsema

    Dave Brondsema - 2014-07-15
    • Can you output a list of all the ticket numbers being moved, as a separate file. SourceForge will need that to be able to set up redirects.
    • Can you get a list of top-used owner/QA/comment usernames? We may want to set up users on forge-allura.apache.org for them.
    • ticket['status'] != 'deleted' -- there aren't any with this status, but no harm really
    • indent=2 on json.dump can be helpful
    • I'm seeing a lot of relatively recent closed tickets end up with milestone "asf_release_1.0.0" but should be "unreleased". One example is #7401 I think we should check for commit messages between asf_release_1.1.0 and current 'master' too.
    • s/wontfix/wont-fix/
    • The custom_fields section of the JSON should be updated to drop size and QA, and add Reviewer (I think it needs to be _reviewer too, since all custom fields start with an underscore). Also the milestone field in that section should be updated to the few new milestones instead of the lots of SourceForge sprint milestones.
    • status: in-progress --> code-review
  • Dave Brondsema

    Dave Brondsema - 2014-07-18
    • status: code-review --> in-progress
  • Dave Brondsema

    Dave Brondsema - 2014-07-18

    Looks like we need an empty saved_bins field:

      File "/home/dbrondsema/dbrondsema-1019/forge/ForgeImporters/forgeimporters/forge/tracker.py", line 163, in import_tool
        self.process_bins(app, tracker_json['saved_bins'])
    KeyError: 'saved_bins'

    Lots (maybe all) open/review/in-progress tickets are ending up with no milestone set. They should go into 'unreleased'.

    This may be different than what I said before, but I think only 'closed' tickets should default to asf_release_1.0.0. For 'invalid' and 'wont-fix' it doesn't make much sense to say those were in milestone asf_release_1.0.0, they should be in 'unreleased'.

    Attachments to a ticket don't get imported. I was looking at ticket 7127 for example. Attachments on a comment do get imported though. Perhaps spin this off into a new ticket, but this will be a blocker.

  • I have fixed these issues, except attachments. In the exported file all the attachment properties are empty: "attachments": [], I think it is an export issue or it was intentionally done this way.

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

    Dave Brondsema - 2014-07-22

    Many are empty (because they have no attachments), but for 7127 I see:

    "attachments": [
      "url": "http://sourceforge.net/p/allura/tickets/7127/attachment/snapshot_border.png",
      "bytes": 12347
    "_id": "52efda3085540d213cb8bc5f",
    "discussion_thread_url": "http://sourceforge.net/rest/p/allura/tickets/_discuss/thread/758182f5/",
    "ticket_num": 7127,
  • Dave Brondsema

    Dave Brondsema - 2014-07-22
    • status: code-review --> closed
    • QA: Dave Brondsema
  • Dave Brondsema

    Dave Brondsema - 2015-01-05
    • Milestone: unreleased --> asf_release_1.2.0

Log in to post a comment.