You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2014/07/22 17:56:45 UTC
[allura:tickets] Re: #7510 Test extracting Allura tickets for Apache move
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,
~~~~
---
** [tickets:#7510] Test extracting Allura tickets for Apache move**
**Status:** code-review
**Milestone:** forge-jul-25
**Labels:** asf
**Created:** Mon Jun 30, 2014 03:47 PM UTC by Dave Brondsema
**Last Updated:** Mon Jul 21, 2014 07:06 PM UTC
**Owner:** Alexander Luberg
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.
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #7510 Test extracting Allura tickets for Apache move
Posted by Dave Brondsema <br...@users.sf.net>.
Created [#7580] for this
---
** [tickets:#7510] Test extracting Allura tickets for Apache move**
**Status:** code-review
**Milestone:** forge-jul-25
**Labels:** asf
**Created:** Mon Jun 30, 2014 03:47 PM UTC by Dave Brondsema
**Last Updated:** Mon Jul 21, 2014 07:06 PM UTC
**Owner:** Alexander Luberg
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.
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.